[tridyman]

pretty big step toward the hack, at Puerto Rico there is a log in on the card but it is a big step.

source where you got this info from?

[seaboard18]

Originally Posted by tridyman

pretty big step toward the hack, at Puerto Rico there is a log in on the card but it is a big step.

Tridyman,

I take it that you have seen this log. I would like to know a few things about the log. Do you see any 256 byte strings? If so, where at in the log do you see them?
Can you give us a few of the command sequences?

Did you know that the current version of the AMD29LV320D TSOP uses the following Security features:
Current version of device has 64 Kbytes; future versions will have 256 bytes Factory locked and identifiable: 16 bytes (8 words) available for secure, random factory Electronic Serial Number; verifiable as factory locked through autoselect function. ExpressFlash option allows entire sector to be available for factory-secured data.
These chips are used in older model 301.013 IRD's, but N2 is reported to use 256 byte strings. I have seen some N2 data from the stream, please post some of the log so that I can compare it to what I have seen. My bet, you have not seen the log, much less the data from the stream unless you can prove it now. Please post some of the log.

[skinerd]

The AM29LV320D flash chip is used in 301-013s and 510 receivers, other flash chips are also used, but those chips are used too. The locked sectors have no bearing on a N2 hack, they could have a bearing on the new receivers being hackable, but that would apply for N1 or N2. I doubt the security features are used even on the newer, 311 etc, receivers, but they very well could be.

[qwerty5]

these chips are being used and they all allow the manufacturer to writeprotect the last sector, a command is issued to the chip to lock or unlock the writeprotect feature, some dp301 receivers out there have the sector locked many dont, if the command to unlock the sector is added to jkeys and such programs will be no problem to write to the whole chip, i have one of the irds with the last sector writeprotected, and collected all the materials about the chip, my ird is also with moved data, never affected jtaging the receiver, the firmware can be full read, while programing writing to the last sector fails, this affects the firmware checkum and some of the ird info screens when i take a stream update, otherwise fully functional, the way around it i go to my original firmware and let it stream update then no problem i dont need to write to the last sector, apparently neither i nor dish is writing to it. i doubt any implementation of the feature and nagra2 but if occurs hope the fun begins, the information is out there on how to writeprotect or unprotect the sector its fairly documented by the manufacturer, so i dont see a problem

[qwerty5]

the 320 and the 160 allow the manufacturer to lock the last sector describing that it can be used to hard code some serials etc, I explained the sector can be read as any other sector just can be locked in other words write protected

[gunther]

The entire purpose of the Vid mod's we do it to give us the ability to unlock these sectors for writing at will.