However whatever You’re dealing with digital Data!
It could be any type of file, video, EEPROM data, music, photos, pornography, whatever, insha’Allah🤞
This is how the data looks like, behind the scenes!
Wherever this data is stored or generated,
…in some way, this data may have to move between, through different locations!
Could in the same device, from a memory card to a screen’s buffer memory!
If You don’t wish to continue read nonsense,
click HERE to download
USELESS FILE CHECKSUM TOOLS
Could 👇be in a vehicle’s control systems from ECU’s, A, B, C, D, E, etc🤷♂️!
That data could be moving from JAMAICA to KENYA, GHANA, BARBADOS, BOTSWANA , TRINIDAD, etc!
Continue to Imagine, or just for example👇
As the data is moving from JAMAICA to KENYA, somewhere somehow, the ‘Babylon’ European colonialists edit or corrupt this data‘s message!
May be the data’s message from JAMAICA was;
“No goh drink liquor”,
but before reaching KENYA as it reached somewhere in England, the colonialists changed it to;
“Now goh drink liquor” !
You see how KENYA will instead, immediately now go drink liquor, get drunk😁😂🤣, then the colonialists easily do their game🤷♂️!
Obviously ‘HAPA UJANJA tu‘ done to data by the colonialist, a.k.a Babylon🤣😂😁!
See how KENYA‘s now blinded, binded + bound & locked up🤷♂️!
Yaani 😁😂🤣recolonized, KENYA system messed up just because of the message’s data that was corrupted, by the ‘Babylon‘, seen🤔?
Alafu don’t just be silly🤣😂😁, relate the ‘Babylon’ colonialists to any nonsense that could trouble the data, to cause errors during transmission, storage, or processing, for example;
Network interruptions like a dropped or unstable internet or network connection!
Third-party interferences like the external software or hardware interfering with the data transfer process.
Could be faulty storage devices, as in, hardware’s or so🤷♂️!
Now, continue to imagine🤔, same story!
JAMAICA wants to send a message, 5021
To make sure that KENYA can realize if the data is or not changed, JAMAICA counts & adds all the digits!
The message could look like;
KENYA gets the message’s data, 5021, but verifies whether it adds up to 8!
This 8 is an example of a CHECKSUM!
So, a checksum is a small value derived from a larger block of digital data used to detect errors that may occur during transmission or storage, seen🤔?
The sender, JAMAICA, calculates a checksum from or using the original data, 5021, and sends it along with the data to the receiver, KENYA.
The receiver then performs the same calculation on the received data and compares the result to the original checksum!
If they don’t match, it indicates that the data has been corrupted by the ‘Babylon’😂😂🤪
Even if data, 5021, doesn’t come in order, but may be, 0251 or 1502, as long as checksum is valid, even if fake data😂🤣😜!
Remember, “a correct checksum doesn’t mean the data is correct“, in other words, a matching checksum indicates a high probability that the data is error-free, but it is not a 100% guarantee🤷♂️!
Checksums are used to verify data integrity, that data has been received or stored correctly assuring NO errors, nor changes by the ‘Babylon’ colonialists!
NOT that the data is being hidden from the ‘Babylon’ colonialists!
Instead, Encryption is the ‘ujanja’ used to ensure data confidentiality, as in, to make data unreadable to the ‘Babylon’ ama any others along the way!
So, a checksum tells you if a file has changed,
while,
…encryption prevents who can read the file in the first place.
If You don’t wish to continue read nonsense,
click HERE to download
USELESS FILE CHECKSUM TOOLS
CHECKSUM is NOT just about summing, adding numbers🤷♂️!
What if the data is NOT numbers?
For example:
X) The President of the INDIAN OCEAN usually gives out envelopes with money!
Or…
Y)Tells His assistants to hand out the money envelopes!
How would a system verify if the correct money is handed out?
A “specific” given system that knows the specific weight, length X, width Y, of the money, could just do some magic, algorithm, to create a reference checksum of it’s own!
There are some standard, international CHECKSUM algorithms known as hash functions, that are used to provide “standard checksums” for any file’s integrity verification!
Briefly, it’s that blaa bla of,
MD5 (Message Digest 5),
SHA (Secure Hash Algorithm) family:
SHA-1, SHA-2, SHA-3, SHA-4, SHA-etc!
For example,
using the the standard color codes
👇
For the same photo👇,
a standard CHECKSUM software used by someone in GHANA,
returns the same CHECKSUM results as that used by someone in BARBADOS,
for this same photo👇
👇
Along the way, should however tiny a dot be,
it changes the data setup in this photo,
and so a checksum error will be reported!
So is why anyone can randomly verify the validity of anything, using any random, but standard checksum tool🤷♂️
If You don’t wish to continue read nonsense,
click HERE to download
USELESS FILE CHECKSUM TOOLS
Coming back to control electronics,
different brands, manufacturers, use various proprietary, unique checksum algorithms that could be specific to the device, model or data block,
rather than a single, universal algorithm for every, BOSCH, DENSO, SIEMENS, NOKIA, SOZI, etc!
Any changes to the electronics’ memory require recalculating the checksum to match the new data.
The original checksum will not correspond with the altered data, which as explained above will leave the whatever ‘KENYA’ system locked up😁😂🤣!
To ensure the control unit functions correctly, a new checksum must be calculated after any modifications, aligning the checksum with the updated data. Seen?
When modifying a memory’s data, it’s crucial to avoid altering that data outside the designated checksum area, as this can interfere with external checksum calculations !
The exact CHECKSUM calculation rules are uniquely developed for for a specific, and non-standardized across all units.
So is why We accumulate and keep packing every CHEKSUM that there is🤷♂️!
These useless tools will alert you if you’re making changes outside these bounds, and it’s best to heed these warnings to prevent potential issues, seen🤔?
If a certain Control unit’s CHECKSUM magic is as shown👇,
NOT every control unit’s will be as so🤷♂️!
If a certain Control unit’s CHECKSUM magic is as shown, NOT every control unit’s will be as so!
Remember, it could be the other irrelevant software’s on your computer, or hardware’s like wires, lose sockets, etc, that causing You ‘checksum error’ nonsense🤷♂️!
Yes, ndiyo, excessive cable length, (along with poor quality or damaged cables), is a common cause of checksum errors.
These web based tools could be of use🤷♂️!
(click to test if you wish, jazkaAllah🤞)
