What i've done was to download this sector from several NX units i have in access, and other dumps i have access to and write it onto my test-unit. In all cases the PIN associated with the device the sector came from, can be entered in the test-NX
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
I still have no clue where the PIN is coded and how, but it's there somewhere. The sector itself is hex 0x1FFFF Bytes in size (131.071 Bytes decimal) but only 0x389 bytes are "used", the others are "0xFF". The location the PIN is stored could be narrowed down by using a binary tree algorithm. Put the lower half of the original sector and the higher half of the other sector into one new sector. Flash it and see if the original PIN still works. If so, the higher half has no meaning for PIN calculation. Go on and split the lower half into two pieces, doing the same as before. Until it doesn't work anymore, then use the upper half of the remaining chunk until it narrowed down to a small amount of bytes.
Maybe it's possible to find the area, but it doesn't mean that it is usefull, because i expect the PIN to be crypted by an unknown algo. I don't expect a real number to find, no no. But having the memory location of it may help to search the code accessing this location, which in turn would be the subroutine checking the input against the stored PIN hash. If the routine is found, it may be patched to always return a positive result, or to inspect the calculation and build an pincode calculator yourself.
You can find many other usefull information in this sector also, like the Ford-partnumber, the BOSCH-partnumber...
For you guys who want to play with it, i attached a sector 507 having the pin 9823. Would like to receive some other samples from you to compare the contents
![Wink ;)](./images/smilies/icon_e_wink.gif)