Do we know that the flash ram is write protected after the attack?
Sent from my GT-I9505 using Tapatalk
You are correct the possible write protect was taken from the end of a log from the other thread. There could have been any number of reasons for this from wrong connection, invalid security key (if needed) even corrupt flash memory, etc. Can you run fsck on flash memory?I don't believe it is left write protected after the attack. The idea that it was I think came from a log file that somebody here posted where one of the last errors was a write error but from what I can tell this was a result of the flash being wiped which meant that the file system that enigma2 was using was wiped from under its feet.
You are correct the possible write protect was taken from the end of a log from the other thread. There could have been any number of reasons for this from wrong connection, invalid security key (if needed) even corrupt flash memory, etc. Can you run fsck on flash memory?
The way I see it is if it was write protected by an upgrade then surely this can also be changed to read/write by the same method! It is highly unlikely that a flash memory can be given the write protect command and then that becomes permanently write protected.
- Get the datasheet for the Samsung K9F2G08U0B TSOP48 ?
Instead of only talking as on the other topic, let's get more technical and post some technical things...
Who is able to :
- Dump the Flash chip they will receive from the manufacturer ?
- Dump the erase Flash chip from the killed receiver ?
- Get the datasheet for the Samsung K9F2G08U0B TSOP48 ?
This will answer your questions about the security/lock/chip.
Please post here,
Omni
Is this what you are looking for? if not then delete it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.