Changes

The figure below is an example of the Flash New Firmware Image section and the table below provides information on the fields contained in that section:

The figure below is an example of the Flash New Firmware Image section and the table below provides information on the fields contained in that section:

[[File:Networking_rutos_manual_firmware_modem_{{{mobile}}}_v1.png|border|class=tlt-border]]

{{#ifeq: {{{series}}} | TRB1 | [[File:Networking_rutos_manual_firmware_modem_{{{mobile}}}_v2.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_firmware_modem_{{{mobile}}}_v1.png|border|class=tlt-border]]}}

<table class="nd-mantable">

<table class="nd-mantable">

When you upload a firmware image, the device will have to verify the validity of that image. If the verification was successful, you will be redirected to window with a message such as this:

When you upload a firmware image, the device will have to verify the validity of that image. If the verification was successful, you will be redirected to window with a message such as this:

[[File:Networking rutx manual firmware verification v2.png]]

[[File:Networking rutx manual firmware verification v2.png|border|class=tlt-border]]

This means that the uploaded firmware image is compatible with your device. The indication also displays the file's Checksum. A <b>checksum</b> is a sequence of hexadecimal symbols generated after running an algorithm called a cryptographic hash function on a file. Calculating a checksum and comparing it with the one provided by the file source can be used as a file authenticity check method.

This means that the uploaded firmware image is compatible with your device. The indication also displays the file's Checksum. A <b>checksum</b> is a sequence of hexadecimal symbols generated after running an algorithm called a cryptographic hash function on a file. Calculating a checksum and comparing it with the one provided by the file source can be used as a file authenticity check method.