0zone
03-13-2006, 12:40 PM
c0d3sP4c3 - ROM 102 Blocker v4.1 Auto Lock - BEV - Public Release Date: 03-11-2006
Features:
This blocker provides the same protection as other blockers with 1 additional feature.
No need to worry if you forget to lock your blocker.
If you forget to lock it-it will lock itself when you insert the CAM into the ird.
This provides an extra level of protection not provided by other blockers.
Another benefit to this blocker is that you can unlock the card and read/dump the CAM
to get keys and not have to spend time relocking and rewriting the CAM afterwards.
You can unlock the card, read it, then stick it back in the receiver without spending
all the additional time just to relock it and without comprimising the safety of your card.
In addition (for those paranoid types) you can manually lock it if you choose before applying it to the
card image by changing the following line from this, $906F100, to this, $906F101. This way you have a choice
between manually locking it or letting the autolock feature do it for you.
Application:
Before you apply the blocker clean the codespace back to Rev 240.
Then cut and paste the full blocker into the patch window of N2Edit Beta 7.
Edit the password towards the bottom of the patch where indicated to the one you want to use.
Apply the patch, and if successfully applied save the card image as a backup.
Write your card image and your done.
How it works:
Current blockers work by monitoring the EMM commands processed from decrypted EMM's and either block or pass
certain ones based on their function and risk to the card. This blocker does that also.
The autolock is activated when the first valid decrypted EMM is sent to the card before anything else is done.
The card will be locked immediatly after bootup comands are processed. Once the card is locked the intercept
used to read/write your card will be disabled until you unlock it. This prevents the provider (Dish) from
explointing the intercept and looping your card. The autolock feature will not lock when "dirty" EMM's are used
with the intercept to r/w the card. You don't have to worry about it interfering with the read and write procedure.
Features:
This blocker provides the same protection as other blockers with 1 additional feature.
No need to worry if you forget to lock your blocker.
If you forget to lock it-it will lock itself when you insert the CAM into the ird.
This provides an extra level of protection not provided by other blockers.
Another benefit to this blocker is that you can unlock the card and read/dump the CAM
to get keys and not have to spend time relocking and rewriting the CAM afterwards.
You can unlock the card, read it, then stick it back in the receiver without spending
all the additional time just to relock it and without comprimising the safety of your card.
In addition (for those paranoid types) you can manually lock it if you choose before applying it to the
card image by changing the following line from this, $906F100, to this, $906F101. This way you have a choice
between manually locking it or letting the autolock feature do it for you.
Application:
Before you apply the blocker clean the codespace back to Rev 240.
Then cut and paste the full blocker into the patch window of N2Edit Beta 7.
Edit the password towards the bottom of the patch where indicated to the one you want to use.
Apply the patch, and if successfully applied save the card image as a backup.
Write your card image and your done.
How it works:
Current blockers work by monitoring the EMM commands processed from decrypted EMM's and either block or pass
certain ones based on their function and risk to the card. This blocker does that also.
The autolock is activated when the first valid decrypted EMM is sent to the card before anything else is done.
The card will be locked immediatly after bootup comands are processed. Once the card is locked the intercept
used to read/write your card will be disabled until you unlock it. This prevents the provider (Dish) from
explointing the intercept and looping your card. The autolock feature will not lock when "dirty" EMM's are used
with the intercept to r/w the card. You don't have to worry about it interfering with the read and write procedure.