View Full Version : How to prevent Unknown Provider
How to prevent Unknown Provider....
Many people are ending up with an Unknown Provider situation on their ROMs. Many times this can be easily avoided. I will try to explain what I mean assuming you are using N2Edit, but the same theory applies no matter what utility you use.
So you have gotten Unknown Provider….This means your card has got it's codespace messed up. This is probably due to not cleaning the image before you added the blocker code. Then when you write it to the card….WHAMMO…. Unknown Provider.
I know you think you cleaned, but the proper order is WITH the EEPROM loaded into your utility of choice, clean the codespace, then apply the blocker to the image, then write it to the card.
It’s still a little confusing to many people.
When you open a card image from your hard drive, it may or may not have been cleaned before it was saved. When you patched your blocker code onto the uncleaned EEPROM that that you loaded, you had parts of the old code, plus the new blocker code. Unknown Provider is what happens when the codespace is not right. Its security protection built into the card.
Still think you cleaned your stuff… Well maybe you did and it’s just a freak of time and space, but maybe you just think you did. If you read your card, then cleaned, then opened an image, then patched your blocker….well…… that’s the problem I’m talking about. I can’t tell you how many people tell me this is what they did and now have UP.
I’ll try to break it WAY down for those that need more help. Many of you already know this, but many other do not. I just hope this helps someone. READ ON.
******************************************
You have a card image on every card. When you unlock the card, you are able to read and write card images to and from the card. When you first open N2Edit, before you do anything, there is no image loaded at all. You have images on your cards and on your hard drive, but not in N2Edit yet...
There are two ways to get a card image into N2Edit.
(1) read your card
(2) open an image from your hard drive.
That’s it.
Now if you already have an image loaded by either method, and you load another image, by either method, you still only have one loaded into N2Edit. Which ever thing you did last, is the one that is loaded.
SO..... what does this mean you may ask???
You probably unlock the card with a password and then read it right? This loads the image from your card into N2Edit like I described above right? If you looked at that image, you would see it was REV10B, or whatever your blocker spoofed the rev to last. At this point, you could just do a "tools" "Clean Codespace" from the dropdown menus and you would then be back at Rev103. No need to load another image from the hard drive because you now have a cleaned image loaded in N2Edit that already contains your IRD#, Boxkeys, and Tiers….. If you open another image from the HD then you are overwriting what you just read from your card.
Does that make sense? You may be doing too many steps. Either don't bother reading your card after you unlock it, or if you choose you can read it and clean codespace. Either one or the other. Then you clean, and then you patch with the blocker code.
This is where people get confused about cleaning. They always say "BUT I CLEANED CODESPACE", but after that, they opened another image from the hard drive that may or may not have been cleaned. If it wasn't cleaned, and then they just patch the blocker, they end up with Unknown Provider.
Even if you don't understand what I'm talking about there is one simple rule that if followed, will greatly reduce the risk of your card going unknown provider. Here is that rule.
RULE: Always Clean Codespace RIGHT BEFORE you patch with your blocker.
If you follow that rule, it will prevent this from happening.
Hope this helps someone
hacker
11-18-2006, 04:31 AM
Thanks for that info ohms! I usually unlock,read,clean,write. Then I read again and make sure it is rev 103. Then I open my AIO and write to card. Never had any problems with that! Do you think what I am doing is ok ohms? Thanks
hacker
you said "I usually unlock,read,clean,write. Then I read again and make sure it is rev 103. Then I open my AIO and write to card. "
the first part. unlock, read, clean, write is more or less safe to do. This only puts a nice clean rev103 image onto the card. Should be no problem.
the last part depends on the condition of your AIO. I assume that since it's an AIO, that it is already equipped with good codespace. However you should understand the following.
When you write your AIO to the card, you are overwriting the nice clean image you just wrote to the card. So what's the point in your first step?
It would be the same result if you did this.
unlock, open AIO, write to card.
1. It's important to understand the principals of card image management.
1. Unnecessary reading and writing to the card puts it at risk of being looped if something goes wrong during the unnecessary write. What if the program locked up? What if the PC rebooted? Your card could be toast.
Only do to the card what is needed. Never read and write unless there is a reason for it. It will probably be fine, but why take the risk?
I guess I should say what the difference is between an EEPROM image and a patch.
When you read your card, you are getting the EEPROM image into your utility like N2edit. This is the entire EEPROM.
When you patch an EEPROM image that you have loaded in N2Edit, whether you read it from the card or opened it from the hard drive, you are just replacing part of the full card eeprom image with the code in the patch.
a patch such as a blocker does not contain the entire codespace. Juts the portions that need to be updated from the clean (usually rev103) image.
This is why you need to clean before you patch.
hacker
11-18-2006, 04:50 AM
Thank you ohms! So you are saying I shouldn't clean codespace, and just write the AIO?
not exactly that simple. I don't have your AIO and I don't use AIOs, so I can't really tell you if what you are asking is 100% true.
Let me ask you a question to find out. What size is the file? If it's 18k, then it's the entire EEPROM image so when you write that to the card, it will overwrite the entire EEPROM image that is on your card.
Don't you need to update keys and blocker code? Or do you just get a new AIO when the keys change. Sorry, but I really don't know how these AIOs work exactly. Do you open the AIO in N2Edit and then patch with something to update the keys? Do you open the AIO with a hex editor and manually update the keys?
hacker
11-18-2006, 05:01 AM
The AIO I have auto rolls. I am using an AIO I made with mr. tierworks. It has p's blocker and his 8b add-on. It is 18k
so just unlock your card, and write the aio. same result as what you were doing before. No point in cleaning something you are just going to turn around and overwrite.
Make sense?
hacker
11-18-2006, 05:04 AM
Ok, thank you!
lefty
11-18-2006, 05:11 AM
As I've been doing it:
Using the original bin that matches my card, I clean codespace, setup my tiers, patch the 3M, change my locals, timezone and zip data, then the blocker. I save that image as my working bin image named 'current'.
1. Reset Card
2. Unlock Card
3. Read Card
4. Open the 'current' image from the HD
5. Write the image to the Card
During these recurring key changes, I run KeyGrabber and let it update my 'current' bin image, it renames it with a suffix to the filename (current-XX)
I use that 'current-XX' bin image from the HD to write to my Card.
Should I abandon number 3? It's unneccesary if I read your post right. So far I've no card go unknown provider. You make a good point though about the PC, the program and power outages. I keep my PC and the programmer on a UPS.
As I've been doing it:
Using the original bin that matches my card, I clean codespace, setup my tiers, patch the 3M, change my locals, timezone and zip data, then the blocker. I save that image as my working bin image named 'current'.
1. Reset Card
2. Unlock Card
3. Read Card
4. Open the 'current' image from the HD
5. Write the image to the Card
During these recurring key changes, I run KeyGrabber and let it update my 'current' bin image, it renames it with a suffix to the filename (current-XX)
I use that 'current-XX' bin image from the HD to write to my Card.
Should I abandon number 3? It's unneccesary if I read your post right. So far I've no card go unknown provider. You make a good point though about the PC, the program and power outages. I keep my PC and the programmer on a UPS.
Mine's on a UPS too, but still I had a card get AFU because of a failed write. You just never know, although a failed read is probably no biggie unless there is a power surge. Your steps are not so risky of UP because you are using a "good" image that you already know has a valid codespace. All you are doing is updating the keys on the image and rewriting to the card. In this case, your step 3 is not doing anything for you since you overwrite that info when you open the image from the hard drive. It's mostly when people patch a blocker to an uncleaned codespace that UP happens.
mackscb
11-18-2006, 05:52 AM
I have always read that you should write a clean image to the card before writing the blockered image to it. I assume this is the same reason as patching an image from the hard drive that may not have a clean code space. So my procedure is as follows.
1)unlock card
2)read card
3)clean codespace 3 times
4)write this image to card
5)optional - reset image, should read rev 103
6)load bin file from HD, usually with tiers already added (or could be an AIO).
7)in my case, I know the image is at rev 103 (clean codespace), but if you are not sure, clean codespace 3 times. Be carefull here. If you are using an AIO it should already have a blocker on it, and if you clean the codespace, you will remove the blocker.
8)patch blocker.
9)patch addon if you are using.
10)save this image. This is important if something goes wrong. you can see what you wrote to the card.
11)write to card.
12)try to read card. It should fail. This means your blocker is working.
I know this is an extra write to the card, and every write to the card carries risk, but it is recommended (safe) way from all my reading.
There very well could be merit to this theory, although I don't know what it would be. Please understand that I am no coder and by no means know more than most about these things. I'm just reporting what I have seen through observation and been told by very very smart coder guys.
I could be wrong. I often am. :)
All in all, I believe that mackscb's procedure is as safe as any. Although I don't know why having an 18k image on the card has any bearing on writing a new 18k image to the card, but like I said, I could be wrong.
mackscb
11-18-2006, 06:02 AM
Actually, I agree. It is probably belt and suspenders, but at $200 per card, it pays to be safe.
Exactly right mackscb. These cards are too expensive to be writing to if you don't know what you are doing. That's why I thought I would post this so that folks might avoid messing up cards. They can be revived from this state most of the time, but still, that is another risk you just don't want to take.
Exactly right mackscb. These cards are too expensive to be writing to if you don't know what you are doing. That's why I thought I would post this so that folks might avoid messing up cards. They can be revived from this state most of the time, but still, that is another risk you just don't want to take.
I agree 100%, everytime you put that card in a programmer....we're dealing with that bastard, Murphy! ;-)
PS that was a good tutorial, you should do a text file and upload here!
Dr Zapola
11-18-2006, 06:47 PM
So in N2 when you CLEAN CODESPACE are you cleaning code space on the card or the eeprom in N2.
Once you read the eeprom is still on the card even though you have an image on N2. I thought the principal was to clean the card to prep it for a new eeprom then you load a bin to bring it back to REV103 then clean the CARD again to prep it for an updated with blocker bin to the card.
So in N2 when you CLEAN CODESPACE are you cleaning code space on the card or the eeprom in N2.
Once you read the eeprom is still on the card even though you have an image on N2. I thought the principal was to clean the card to prep it for a new eeprom then you load a bin to bring it back to REV103 then clean the CARD again to prep it for an updated with blocker bin to the card.
In N2 when you CLEAN CODESPACE you are cleaning code of the EEPROM that you have loaded in N2, not the card.
Reading does not change the card one bit.
The only program (that I know of) that cleans the card directly is Romcode. Even then, its just an automated unlock, read, clean, write process that is done with the click of the clean button. CORRECTION : Thanks to Satan, I download N2Edit 2.5.8 and found it has a one step clean script just like Romcode
some have said you need to have a clean image on the card before you write anything to it. I can not tell you with 100% certainty that this is untrue, but I believe it to be. The card holds an 18k binary file in it's eeprom. When you write an 18k card image to the card, you are overwriting this file. Unless the card is locked, what does it matter what you are overwriting? As I have said before, I could be wrong about this. If anyone KNOWS otherwise, please chime in and explain it to me.
Dr Zapola
11-18-2006, 07:08 PM
So then why not take your virgen REV 103 bin and clean it on N2 then save to file then next time load the saved allready cleaned bin so you dont have to go through that step.
Now your talkin!!!! Save a clean bin and don't bother reading your card at all. Just unlock it. Then load your clean bin, patch it with whatever you need like blocker/tiers/keys whatever, and write that sucker to the card.
Perfect!
Dr Zapola
11-18-2006, 07:19 PM
OK. So what am I cleaning off my bin. Why is it there. Was it put there by the writer, I mean the guys that made GopherX public fix didnt they make it with all the needed stuff and when we use clean code space where removing some of the info in the bin. Dont I need all the info to make my card work
When you clean codespace, you are returning the card back to rev103 status, with no blocker code on it. dataspace is where all of your info is for tiers and session keys and ird# and boxkeys and stuff like that. It remains untouched when you clean the codespace.
Lets be clear. A bin is a file. It's a binary copy of what is on the EEPROM. It is 18k and contains both codespace and dataspace.
Since most blockers are patches, they are designed to replace some of the code in the codespace. In order to know what the end state of the codespace will be, one must know exactly how it is when you start. By cleaning codespace, you are putting the card into a known state of code. At this point, the blocker patch will replace just certain pieces of that codespace, and the rest will remain as it was.
If you didn't clean codespace before you patched your blocker to it, then you might now have the starting point that the blocker was written to update.
Does that make sense?
Satan
11-18-2006, 07:53 PM
N2edit 2.58 has a one step clean in it..what this does is write a clean image to your card..or Icam..it can tell the diff. You have to have a clean image on the card before you write to card\Icam....If you don't..say you had Pengas v28 AIO image on your card.....you unlocked it with password.....and than loaded Hack_kid's AIO and wrote to card...card goe's U\P
Reason is ....that Penga's blocker and hack_kids blocker write to diff sections of the card...so what you'v just done is overwriten the orignal Penga blocker with the hack_kid blocker . NOT GOOD !!! Cleaning code space will not do anything for you...it doe's not effect the card...it simply cleans the codespace in the image your about to write to card. If you clean the codespace on the hack_kid's AIO ...than don't bother writting it to card...as you'v just wipped the blocker off...LoL
Use N2edit 2.58...do a one step clean this not only cleans codespace..it write's a virgin imae to the card\Icam...there's no codespace to clean...LoL. Open the bin you want to load and write to card. end of story.
N2edit 2.58 has a one step clean in it..what this does is write a clean image to your card..or Icam..it can tell the diff. You have to have a clean image on the card before you write to card\Icam....If you don't..say you had Pengas v28 AIO image on your card.....you unlocked it with password.....and than loaded Hack_kid's AIO and wrote to card...card goe's U\P I don't understand the above. Are you saying that Pengas v28 AIO contains binary information that is outside of the 18k card image binary file? If you wrote a full 18k card image binary file to the card, wouldn't you be overwriting the old Penga code in its entirety?
Reason is ....that Penga's blocker and hack_kids blocker write to diff sections of the card...so what you'v just done is overwriten the orignal Penga blocker with the hack_kid blocker . NOT GOOD !!! I totally agree with this part. However I think I only agree if we are talking about patching hack_kid over the top of Penga blockered codespace.
Use N2edit 2.58...do a one step clean this not only cleans codespace..it write's a virgin imae to the card\Icam...there's no codespace to clean...LoL. Open the bin you want to load and write to card. end of story.I don't believe this addresses the issue of how people are getting UP state. The Onestepclean does write cleaned to rev103 codespace to the card. But if you overwrite that cleaned codespace with AFU codespace by writing another bin, then your nice clean card has done you no good
Satan
11-18-2006, 08:25 PM
Part 1
Penga blocker's write the password at 9878 I think....hack_kid write's the password at 3350 (I'm not sure on the number's and I have to get to work..LoL)
Pengas blocker start's at xxxx and ends at tttt hack_kids starts at eeee and ends at yyyy so when you over write one to the other you'v made a wicked mess of the bug table...password is being written to a loaded section of the card..ect ect
part 2
unless you write a virgin image to your card..your going to have to overwrite the first blocker....how can you not..?...that's the purpose of the one step clean ...to clean the codespace..?
part 3
not even sure I understand what your asking..?..LoL
you have to have a clean vigrin image on the card in order to write anything to it safely. if your not cleaning the card than your writiing over something...LoL This has never been an issue..?..we wrote clean bin's to our cams in the rom 3 10 11 day's before apply new scripts to it...?. Now a day's there 6 or 7 diff blocker's on the market ...so if you want to try a diff one..you'd better make sure your applying it to a clean card. %99 of the U\P on the penga blocker is due to the fact that he changed up the bug table setting's and no-one was cleaning the card.
PS: this is also the reason you must write a virgin dish image to a bev card before you try and apply a dish script to the card...the codesapce on a bev card contains bev info ...try overwriting a dish image to a bev cam and you'v just fryed your card...you'v simplt tryed to write codespace data over an already loaded section of the card
Thank you Satan (I never thought I would say those words) LOL
I appreciate the dialog. I usually learn something from everyone else's experiences so I always appreciate the back and forth, regardless of the topic. Sorry you have to go to work on the weekend. :(
Anyway... let me see if I understand what you are saying and how it relates to what I am saying which may actually be the same thing in a round about way.
Part1 comment: I don't think most people write any blocker code directly to the card. If they did, then I would agree with you 100%. I believe most people use N2Edit or some utility to open a card image (both codespace and data space totaling 18k) by either reading the card, or opening a image file. At this point you can pull the card because you are working on the image that is in the application. Once you have this image loaded up into N2Edit or whatever util you like, then you will apply whatever code to the image and write that entire image to the card. Is this not correct so far?
If we can agree on that, then let’s look separately at the process of "applying the blocker code". If the card image you have loaded up in N2Edit contains penga code, and you patch in some codespace code, then you have pieces of both present within the codespace of the 18k image. Write that to the card and you are UP for sure. I think we agree right?
Satan
11-18-2006, 10:20 PM
I work for myself...so it's not to bad...LoL. ya your right on the money ....When I do my 811 ..say the last time I did it....
I use N2edit 2.58
open the last image I wrote to Icam
clean codespace 4 time's this clean's old blocker off image I have open in N2edit 2.58
Tiers stay on image so no need to even touch them
I patch new blocker to the cleaned image
than check that codespace at A500 to A700 will remain clean (this is must on Icams) (not plastic)
To do this:
Take a look at $30C0, it should be something like this...
$30C0=A7BF8703808000000000000000000000
See the #$A7 at $30C0? That says the dataspace begins at $A700.
I than save this image
I open nagramaster 3.8 under tools in N2edit 2.58 and set time zone and change password
Save this image
Do a onestep clean on Icam
must read rom 102 rev 280
MUST READ ROM 102 REV 280...LoL....this mean's I have a clean virgin image written to the Icam
load my saved bin and write to card
reset ATR must be at 102 rev 289 ..just means blocker is on card
watch TV.....All I'm trying to say ..is you must write a virgin image to the card before you apply anything to it....sorta like having a piece of paper on the table ..and lot's of writing on it.....than laying another piece of paper on top of the first ..and useing a felt tipped pen ...writting on the second sheet..... it will penetrate throught the top ..and corrupt the first ....LoL..If you keep piling sheets on and writing over top ...the bottom one will be unreadable in short time The bottem one being your original cam image....The one step clean...clean's the first sheet of paper every time. so when the second sheet's scribbling soaks through ...as it should.... it's the script your applying to the card...you will be able to read the first sheet ...Gawd that's a horrible way of trying to explain it....LmfaO....
Same applys to plastic ya can't just keep sticking the card in the ISO and unlocking with password and applying a new bin's \ images to card.without cleaning the card first.
Well bud, I know for a fact that you are a real smart guy and a seasoned tester, so I don't want to argue with you. I must be missing something though cause I don't get the need to have a clean image before you write a new image. Just don't think that's right, but it might be. I guess we will have to agree to disagree on that fine point.
The bottom line for folks reading this thread is that Satan's method will result in a correctly programed card and no Unknown Provider. That I am sure of.
I wish one of the super smart plastic guys that have a in depth understanding of the relationship of the codespace and dataspace and how they sit on the card would chime in on this. I mean someone like DogBreath or Gooding or any of the other superbrains.
Satan
11-19-2006, 01:30 AM
LoL...no prob. not argueing ..or upset...more like amused..LoL. if you unlock your card ...rad it..than save the image....say call it *poon* ...load the poon in N2edit 2.58 and take a look at the eeprom.
Open a diff AIO image in a new N2edit 2.58 and do the same. take a look at the eeprom ...compare the two..side by side...I'd bet the dog and g\F that they differ in many way's...diff info at diff lines.
I know ya can't do this....but say ya could...lay one on top of the other..they won't match up ...line $cd20 will be xzxxxrzzrxrzrz ..on the one image and the same line on the other will be fgtfffggtfff,,or whatever...LoL.
When you overwritwe the image's ...one on to the other...your gonna get a line that will look like
$cd20 :xrffxggrxtxg...LoL....or something like that .
When you write a virgin image to the card you have just written $cd20:00000000000000 to the line.....
Just the safe way to do it.....I'v never lost a card in the 10 or whatever year's I'v been in the hobby...Shouldn't really say that....as I did a big boo-boo on a 102...LoL...but that was due to a lil to much drinking...and a lil wild codeing...LoL.
I'm with ya man. Actually, the new nagramaster 4x has a bin compair utility built in that I have used quite a few times.
For some reason, we are not communicating very well. I think you are missing the point of what I am saying.
When you write an image to a card, you are not updating part of that eeprom on the card and leaving other parts as it was. You are writing all offsets from the start of the eeprom to the end.. all 18k with no gaps.
so how can there be leftover code on the card from before you wrote the card image?
Dr Zapola
11-19-2006, 02:48 AM
OK. So Satan is saying
1. N2 unlocks the card
2. N2 takes a read and the old eeprom that N2 just copied off the card is now in the N2 tool.
3. When you apply Clean Code space N2 is applying a clean image TO THE CARD.
4. Open virgen image (102 REV103)from files with N2 clean code space of the virgen file in N2 tool.
5. Write virgen image to card.
6. Open updated bin in N2 clean codespace of updated bin in N2 tool.
7. Open patch in N2
8. Apply path to updated cleaned bin in N2.
9. Write to card
10. Read card to conferm blocked works by looking for a read failed indo.
OR OHMS is saying
1. N2 unlocks the card
2. N2 takes a read and the old eeprom that N2 just copied off the card is now in the N2 tool.
3. When you apply Clean Code space N2 is CLEANING CODESPACE OF THE EEPROM COPIED OFF THE CARD THAT IS NOW IN THE N2 TOOL. ( Why clean at this point the old eeprom is not needed, it has old keys)
4. Open virgen image (102 REV103)from files with N2 clean code space of the virgen file in N2 tool.
5. Write virgen image to card.
6. Open updated bin in N2 clean codespace of updated bin in N2 tool.
7. Open patch in N2
8. Apply path to updated cleaned bin in N2.
9. Write to card
10. Read card to conferm blocked works by looking for a read failed indo.
Satan
11-19-2006, 02:52 AM
LoL...I never *read the card* why would I ..?. reset ATR gives me all the info I need.
so Satan... If what your saying is true then riddle me this.
You have a card with penga blocker on it. You unlock that card. You open a clean image on your hard drive and write it to the card. Is there any of the penga blocker left on the card?
Of course there isn't.
Dr Zapola
11-19-2006, 02:55 AM
OK.So at a key change just
1. N2 unlocks the card
2. N2 reset ATR and check info
3. When you apply Clean Code space N2 is applying a clean image TO THE CARD.
4. Open virgen image (102 REV103)from files with N2 clean code space of the virgen file in N2 tool.
5. Write virgen image to card.
6. Open updated bin in N2 clean codespace of updated bin in N2 tool.
7. Open patch in N2
8. Apply path to updated cleaned bin in N2.
9. Write to card
10. Read card to conferm blocked works by looking for a read failed indo.
Crazy1_79
11-19-2006, 02:59 AM
You guys are right, when you clean codespace it merely cleans the eeprom of the card you just read. It does not actually write this clean image to the card. Do you have to write this clean image to the card before patching anything else? The answer is no, you do not have too. by cleaning the image in N2edits memory, you have taken out all blockers. Now patch new code and write it. N2edit compares the card image to the image in memory and only rewrites any data that is different between the two. so by cleaning the codespace first you have accomplished all you need to do. no reason to write that image to the card. LIke ohms said, fewer rights, means less likely chance you will fubar card.
WHEW!!!! I was starting to doubt myself. :)
Crazy1_79
11-19-2006, 03:02 AM
why not read a card? I want the last known working image is why, I read it and start from there, I know it worked so I know it is what I want to work with to get the job done. it don't matter if you don't read, N2edit reads and then writes comparing the eeprom you opened and the eeprom on the card, it only writes the bytes that are not identical.
Crazy1_79
11-19-2006, 03:04 AM
Satan if you hit reset and then hit clean codespace there is no image loaded to clean,
ATR: 3F FF 95 00 FF 91 81 71 FF 47 00 44 4E 41 53 50 31 30 32 20 52 65 76 31 30 42 15
CAM Type: ROM102 Rev10B
Provider: Dish Network
No valid image loaded!
Dr Zapola
11-19-2006, 03:09 AM
OK So cleaning is for EEPROM to be put on the card NOT to clean the card.
Meaning
1. N2 unlocks the card
2. Open virgen image (102 REV103)from files with N2 clean code space of the virgen file in N2 tool.
3. Write virgen image to card. (Brings card back to REV103)
4. Open updated bin in N2 clean codespace of updated bin in N2 tool.
5. Open patch in N2
6. Apply path to updated cleaned bin in N2.
7. Write to card
8. Read card to conferm blocked works by looking for a read failed indo.
step 3 is superfluous, but it won't hurt anything unless the write goes bad.
Satan
11-19-2006, 05:36 AM
Satan if you hit reset and then hit clean codespace there is no image loaded to clean,
ATR: 3F FF 95 00 FF 91 81 71 FF 47 00 44 4E 41 53 50 31 30 32 20 52 65 76 31 30 42 15
CAM Type: ROM102 Rev10B
Provider: Dish Network
No valid image loaded!
I have a saved bin for the 811 on H\D..why would I read the card to get the bin...?..LoL...were sorta going in circles here....I open a saved bin that I know work's...it has the IRD # and boxkey's and a tier pack...than patch the newest blocker and write to a clean Icam...that I'v written a virgin imahe to ..LoL
on the 3100's that I do (I use the public tsop flash's) I simply open a good AIO and write to the card that I'v written a virgin image to ...onestep clean....why would I ever need to clean codespace on any image I'm going to use...cleaning codespace removes the blocker...LoL
Not only that but if I were to unlock card...read card than clean codespace..and apply a new blocker ..The chanch's are more than likely to get messed up by this 3 step procedure...LoL a bad read could become a onestep door stopper...LoL
Plus with the AIO ...you don't have to change anything on the AIO...that's why there called All In One..LoL 811 is a lil diff.
Guess it boils down to a personal choich . doing the one step clean just makes sence to me....and if you feel that it's not required than you don't have to do it...Lot's of folk that were used to just loading Penga's blocker on their card (might tend to agrre with me) ..when he changed up the bug table there were many a card that went U\P...every post for a month ...LoL.
Lot's of folk that were used to just loading Penga's blocker on their card (might tend to agrre with me) ..when he changed up the bug table there were many a card that went U\P...every post for a month ...LoL.
I remember this well. To the best of my understanding, this was caused by peeps not cleaning the codespace before they patched the blocker. Exactly what I started this thread to avoid. Then when that was written to the card, it went UP. It would have gone UP no whether or not you had a clean image already on the card when you wrote it.
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.