Fritzbox 7490 recovery funktioniert nicht

[PeterPawn]

The names do not matter ... the input file has to be a valid firmware image (containing a "var/tmp/kernel.image" and "var/tmp/filesystem.image" file) and output is written to the specified file. This output is simply a combination of the kernel and the filesystem, where a CRC32 checksum was truncated, if it exists.

If you do not understand the syntax of I/O redirection at all, you should read some shell basics first ... it's absolutely worth the time.

And yes ... I mean, you should check some values from your environment (or let us see them) - somewhere the problem with the recovery program must have its roots.

The correct call would be:

image2ram < input_file > output_file

... the (angle) brackets define the input file (after the left bracket) and the output file (after the right bracket).

 

[Pingwing]

Thx for the answer.

Ok, the fastest way to get some detailed information on my FB was by using theruKernel tool for me. Here is the info about FB:

Box-Informationen:
    ProductID:                 Fritz_Box_HW185
    HWRevision:                185
    HWSubRevision:             6
    SerialNumber:              0000000000000000
    annex:                     B
    autoload:                  yes
    bootloaderVersion:         1.1964
    bootserport:               tty0
    cpufrequency:              500000000
    crash:                     [0]7b372997,5772e644,1[1]0,0,0[2]cfb3272,5a8c919d,1[3]0,0,0
    firmware_info:             recovered=2
    firmware_version:          avm
    firstfreeaddress:          0x81116240
    flashsize:                 nor_size=0MB sflash_size=1024KB nand_size=512MB
    linux_fs_start:            1
    maca:                      38:10:D5:2A:03:99
    macb:                      38:10:D5:2A:03:9A
    macdsl:                    38:10:D5:2A:03:9D
    macwlan:                   38:10:D5:2A:03:9B
    macwlan2:                  38:10:D5:2A:03:9C
    memsize:                   0x10000000
    modetty0:                  38400,n,8,1,hw
    modetty1:                  38400,n,8,1,hw
    mtd0:                      0x400000,0x3400000
    mtd1:                      0x0,0x400000
    mtd2:                      0x0,0x40000
    mtd3:                      0x40000,0xA0000
    mtd4:                      0xA0000,0x100000
    mtd5:                      0x0,0x200000
    my_ipaddress:              192.168.178.1
    req_fullrate_freq:         250000000
    prompt:                    Eva_AVM
    sysfrequency:              250000000
    tr069_passphrase:          cbZVD7zS9poi
    tr069_serial:              00040E-3810D52A0399
    urlader-version:           2964
    usb_board_mac:             38:10:D5:2A:03:9E
    usb_device_id:             0x0000
    usb_device_name:           USB DSL Device
    usb_manufacturer_name:     AVM
    usb_revision_id:           0x0000
    usb_rndis_mac:             38:10:D5:2A:03:9F
    wlan_key:                  24745127353986292411

  Flash-/Speichergrößen:
    Memsize:   268.435.456 Bytes (262.144 kB, 256 MB, 0,3 GB)
    mtd0:       50.331.648 Bytes (49.152 kB, 48 MB)
    mtd1:        4.194.304 Bytes (4.096 kB, 4 MB)
    mtd2:          262.144 Bytes (256 kB, 0,3 MB)
    mtd3:          393.216 Bytes (384 kB, 0,4 MB)
    mtd4:          393.216 Bytes (384 kB, 0,4 MB)
    mtd5:        2.097.152 Bytes (2.048 kB, 2 MB)

  ProductID:   Fritz_Box_HW185
  HW-Revision: 185  => FRITZ!Box 7490

I thought to proceed by chaging linux_fs_start to 0 and then flash the new image (coming from the latest international firmware) that i made with image2ram in to the router by using the scripts mentioned here: https://www.ip-phone-forum.de/threads/a-couple-of-questions-on-upgrading-fb7490-english.298201/
(the same link as you gave me)

 

[PeterPawn]

Sorry ... I wrote (intentionally), that you should use "get_environment" (or the PowerShell equivalent). Why? Because the ruKernelTool uses single "GETENV" commands to collect data (that's why values may be missing here, if they were not read) ... and there may be differences (I mentioned it above already, if I'm not wrong) between the output of "RETR env" and single "GETENV" invocations.

If your image was made from the international version of the firmware, your device will not really work ... due to the current value of "firmware_version" you have to use the "german" version or you must change the "firmware_version" value accordingly.

Don't forget to save the log file (or to create one, if you use PowerShell - the Linux scripts save the whole dialog with EVA themselves to a file) for later analyzes.

 

[Pingwing]

Ok got it. It took me some time to understand the eva_get_environment script. I got the famous "illegal option -u" error on my ubuntu computer. I came across a lot of weird suggestions on this forum and heavy discussions, but in the end I found out that I just had to change the first line in the script. From #! / Bin / sh to #! / Bin / bash as stated here: https://translate.googleusercontent...700201&usg=ALkJrhgfT3s23cI57x7vSMT51TgGXV3upg
the output files gave me this:

HWRevision            185
HWSubRevision         6
ProductID             Fritz_Box_HW185
SerialNumber          0000000000000000
annex                 B
autoload              yes
bootloaderVersion     1.1964
bootserport           tty0
cpufrequency          500000000
crash                 [0]7b372997,5772e644,1[1]0,0,0[2]cfb3272,5a8c919d,1[3]0,0,0
firstfreeaddress      0x81116240
firmware_info         recovered=2
firmware_version      avme
flashsize             nor_size=0MB sflash_size=1024KB nand_size=512MB
linux_fs_start        1
maca                  38:10:D5:2A:03:99
macb                  38:10:D5:2A:03:9A
macwlan               38:10:D5:2A:03:9B
macwlan2              38:10:D5:2A:03:9C
macdsl                38:10:D5:2A:03:9D
memsize               0x10000000
modetty0              38400,n,8,1,hw
modetty1              38400,n,8,1,hw
mtd0                  0x400000,0x3400000
mtd1                  0x0,0x400000
mtd2                  0x0,0x40000
mtd3                  0x40000,0xA0000
mtd4                  0xA0000,0x100000
mtd5                  0x0,0x200000
my_ipaddress          192.168.178.1
prompt                Eva_AVM
ptest              
req_fullrate_freq     250000000
sysfrequency          250000000
tr069_passphrase      cbZVD7zS9poi
tr069_serial          00040E-3810D52A0399
urlader-version       2964
usb_board_mac         38:10:D5:2A:03:9E
usb_device_id         0x0000
usb_device_name       USB DSL Device
usb_manufacturer_name  AVM
usb_revision_id       0x0000
usb_rndis_mac         38:10:D5:2A:03:9F
wlan_key              24745127353986292411

and the count:

reboot_major          64
reboot_minor          32
run_hours             2
run_days              2
run_mounths           3
run_years             4

So, for me this information doesn't tell me why my recovery file doesn't work any more (because I'm way to much of a noob here). So I'm planning on proceeding with the tutorial you gave me in this https://www.ip-phone-forum.de/threads/a-couple-of-questions-on-upgrading-fb7490-english.298201/ link @ post #14

I'll use the powershell scripts so I've a log as well. @PeterPawn: Before I proceed, do you see anything wrong in my environment?

### Zusammenführung by stoney ###

So I tried it out with these code's but I get an error:

PS C:\7490\YourFritz-master\eva_tools> .\EVA-Discover.ps1 -maxWait 120 -Debug -Verbose
VERBOSE: Sending discovery packet (1) ...
DEBUG: Received UDP packet from 192.168.178.1:5035 ...
VERBOSE: Trying to connect to the FTP port to hold up the device in bootloader ...
DEBUG: Error during FTP connection attempt ...
EVA_IP=192.168.178.1
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { SwitchSystem }
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { GetEnvironmentValue linux_fs_start }
0
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { RebootTheDevice }
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { GetEnvironmentValue linux_fs_start }
0
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { BootDeviceFromImage image.image }
Exception calling "Invoke" with "0" argument(s): "Error uploading image file."
At C:\7490\YourFritz-master\eva_tools\EVA-FTP-Client.ps1:627 char:21
+                     $ScriptBlock.Invoke()
+                     ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

PS C:\7490\YourFritz-master\eva_tools>

Is there something I missed?

 

[PeterPawn]

Maybe a problem with the firewall or any installed "security suite". But you should truly add "-Debug" and "-Verbose" switches to EVA-FTP-Client invocations ... or do you see any output, which looks like a "protocol"?

The goal was to achieve any further knowledge, why the FTP dialog fails - the script does more or less the same as the actions from the recovery program - but it doesn't take any 'provider' value into account and doesn't check the 'firmware_version' value, before it loads the image into RAM. How do you think, could you get this knowledge, if you do not see any messages from this dialog?

 

[Pingwing]

Firewall is disabled, virus control as well.

tried again:

PS C:\7490\YourFritz-master\eva_tools> .\EVA-Discover.ps1 -maxWait 120 -Debug -Verbose
VERBOSE: Sending discovery packet (1) ...
DEBUG: Received UDP packet from 192.168.178.1:5035 ...
VERBOSE: Trying to connect to the FTP port to hold up the device in bootloader ...
DEBUG: Error during FTP connection attempt ...
EVA_IP=192.168.178.1
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { SwitchSystem } -Debug -Verbose
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.1964 0x0 0x740D

================
DEBUG: Sent
GETENV linux_fs_start
================
DEBUG: Response:
linux_fs_start        0

200 GETENV command successful

================
VERBOSE: current setting - linux_fs_start=0
VERBOSE: new setting     - linux_fs_start=1
DEBUG: Sent
SETENV linux_fs_start 1
================
DEBUG: Response:
200 SETENV command successful

================
VERBOSE: new value set successfully
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { RebootTheDevice } -Debug -Verbose
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.1964 0x0 0x740D

================
DEBUG: Sent
REBOOT
================
DEBUG: Response:
221 Thank you for using the FTP service on ADAM2
221 Goodbye.

================
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { BootDeviceFromImage image.image } -Debug -Ver
bose
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.1964 0x0 0x740D

================
DEBUG: Sent
GETENV memsize
================
DEBUG: Response:
memsize               0x10000000

200 GETENV command successful

================
DEBUG: Memory size found    : 08000000
DEBUG: Image size found     : 0x0185a100
DEBUG: Set memory size to   : 0x067a5f00
DEBUG: Set MTD ram device to: 0x867a5f00,0x88000000
DEBUG: Sent
SETENV memsize 0x067a5f00
================
DEBUG: Response:
200 SETENV command successful

================
DEBUG: Sent
SETENV kernel_args_tmp mtdram1=0x867a5f00,0x88000000
================
DEBUG: Response:
200 SETENV command successful

================
DEBUG: Sent
TYPE I
================
DEBUG: Response:
200 Type set to BINARY

================
DEBUG: Sent
MEDIA SDRAM
================
DEBUG: Response:
200 Media set to MEDIA_SDRAM

================
DEBUG: Uploading file 'image.image' to '0x867a5f00 0x88000000' ...
DEBUG: Sent
P@SW
================
DEBUG: Response:
227 Entering Passive Mode (192,168,178,1,12,8)

================
DEBUG: Sent
STOR 0x867a5f00 0x88000000
================
DEBUG: Response:
150 Opening BINARY data connection

================
DEBUG: Response:
553 Execution failed.

================
DEBUG: Sent
SETENV memsize 0x0x10000000
================
DEBUG: Response:
200 SETENV command successful

================
DEBUG: Sent
UNSETENV kernel_args_tmp
================
DEBUG: Response:
501 environment variable not set

================
DEBUG: Sent
QUIT
================
DEBUG: Response:
221 Thank you for using the FTP service on ADAM2
221 Goodbye.

================
Exception calling "Invoke" with "0" argument(s): "Error uploading image file."
At C:\7490\YourFritz-master\eva_tools\EVA-FTP-Client.ps1:627 char:21
+                     $ScriptBlock.Invoke()
+                     ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

 

[PeterPawn]

It's - due to my own experience - a sure sign for an invalid image file, if the answer is "553 Execution failed.".

The cause may be a (really) wrong image file or a wrong cabling and/or transmission.

If I myself (e.g.) use another FRITZ!Box router as "switch" (that means, I plug the cable from the router in question into another FRITZ!Box, where my PC is connected, too - to circumvent any "media sensing"), I get permanent some errors during transmission of larger files (to EVA only) ... and a new firmware is a larger file.

Please describe (and check) your environment a bit more ... but you should/could check the used image (instead or additionally). Its size has to be the sum of the sizes from "kernel.image" and "filesystem.image" (use 'tar' to extract these files from AVM's image manually for a check) - minus 16 bytes (2 times 8 bytes at each image) from the trailing checksums, which were truncated. If you use "hexdump" on the created image, the string "sqsh" should show up on a 256-boundary - that means, its offset (the first column of a 'hexdump -C' output) should end with two zeros and the string should be the first data on this line (if a width of 16 bytes per line is used).

There's somewhere a - more or less wrong - description in a thread, where a 'dd' utility is used with options, which may be missing from some Linux distros. If you had used this description, you should use my "image2ram" script instead - but that's only one (possible) pitfall, why an image may contain wrong data and therefore can't be started by EVA (what's the reason for the "553" message).

Because the original recovery program fails too, I'd rather expect a cabling or handling error or really a defective Ethernet port - you should use another one next time.

All other transmissions (from reading the environment up to writing a new (and empty) TFFS image) use only short packets, where the complete data is contained in a single payload - so a defective port buffer (at the very last positions, which are only used with "full-size packets") could lead to such an error.

 

[Pingwing]

Thank you for your answer. My setup is indeed a bit unclear. It's a windows 10 computer directly connected to the lan1 port from the fritzbox. In the time the FB was still working I noticed sometimes that LAN port were like acting weird and not always showing al the devices connected. But that was still in the setup phase and it could have been for many reasons.

I'm more thinking of a wrong image file. I used the image2ram script on my ubuntu computer and I took for the source code the latest TAR file for the international market. I'm thinking more in this direction. Since i changed the extension from a .in-memory extension to a .image extansion in the believe that this would make the script work. Maybe that was not the best idea. I've to check it out...

 

[Pingwing]

So I made a new image and in size it looks ok. But the "sqsh" string is no-were to be found in the hexdump. To make the image I used as command:

sh image2ram <FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.53.tar> ToUse

The output from the hexdump is huge. With a search function I couldn't find the string "sqsh" . The last line's of the output are:

01859190  01 f4 cc 03 21 01 08 00  cf f9 26 8f e0 e6 73 53  |....!.....&...sS|
018591a0  f6 5d 00 3f 91 45 84 68  34 8a 09 0a 40 63 a4 e0  |.].?.E.h4...@c..|
018591b0  29 79 87 17 b7 c9 90 d9  83 bb e3 65 a7 83 87 fa  |)y.........e....|
018591c0  25 2a e3 ff b7 f6 40 c6  7c d4 74 f0 91 8e 57 03  |%*....@.|.t...W.|
018591d0  d1 be 3e cc 3f 0d 53 08  39 bf 92 a0 d0 01 e0 d4  |..>.?.S.9.......|
018591e0  d7 50 71 86 f7 8f f7 cb  b0 a9 5f 09 e2 b8 9a b7  |.Pq......._.....|
018591f0  d2 bc c0 e0 86 e3 f5 96  88 d6 b7 bc 1c bc b3 a5  |................|
01859200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
0185a100

I'm not completely sure if this is correct according to your description.

So I tried to upload the image "ToUse" to the FB over the LAN2 port. But the same error occurred.

UPDATE: I've used the recovery program with my linux pc (wine) directly connected to the FB. Tried, every LAN port, but no success.
I do have a switch at home so should I connect my ethernet port from my windows pc to a gate of the switch and the LAN2 (or an other one) to an other gate of the switch? Can that make a difference?

 

[PeterPawn]

I've no idea, where your input file comes from.

My archive contains:

vidar:/home/GitHub/YourFritz/eva_tools # find ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/ -ls
   208931      0 drwxr-xr-x   1  root     root           82 Jul 26  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/
   208932      0 drwxr-xr-x   1  root     root          812 Jan  3 17:05 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch
   208934  26872 -rw-r--r--   1  root     root     27514880 Sep 28 18:15 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.90.image
   208936  23940 -rwxr-xr-x   1  root     root     24514560 Dec 12  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.23.image
   208937  23440 -rwxr-xr-x   1  root     root     24002560 Mar  4  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.05.image
   208938  23920 -rwxr-xr-x   1  root     root     24494080 Jul 16  2015 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.30.image
   208939  26432 -rw-r--r--   1  root     root     27064320 Mar  9  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.83.image
   208940      4 -rwxr-xr-x   1  root     root          185 Feb 11 21:12 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/.listing
   208941  26420 -rw-r--r--   1  root     root     27054080 Jan 23  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.80.image
   208942  23940 -rwxr-xr-x   1  root     root     24514560 Feb  2  2015 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.24.image
   208943  26812 -rw-r--r--   1  root     root     27453440 Nov  9 15:47 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.92.image
   208944      4 -rwxr-xr-x   1  root     root           67 Jan  3 12:21 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/info.txt
   208947  25132 -rw-r--r--   1  root     root     25733120 Feb  3  2016 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.51.image
   208948  25300 -rw-r--r--   1  root     root     25907200 Jul  6  2016 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.60.image
   208950  24532 -rwxr-xr-x   1  root     root     25118720 Aug  8  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.20.image
   208951  25132 -rwxr-xr-x   1  root     root     25733120 Dec 10  2015 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.50.image
   663418  26872 -rw-r--r--   1  root     root     27514880 Jan  2 10:52 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch/FRITZ.Box_7490.113.06.93.image
   208952      4 -rwxr-xr-x   1  root     root          384 Feb 11 21:12 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/.listing
   208953      0 drwxr-xr-x   1  root     root          608 Apr  2  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english
   208954  25532 -rw-r--r--   1  root     root     26142720 May 26  2016 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.52.image
   208955  24612 -rwxr-xr-x   1  root     root     25200640 Aug 27  2015 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.30.image
   208956  26872 -rw-r--r--   1  root     root     27514880 Feb  3  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.80.image
   208957      4 -rwxr-xr-x   1  root     root          291 Feb 11 21:12 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/.listing
   208958  24540 -rwxr-xr-x   1  root     root     25128960 Oct 18  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.20.image
   208959  26932 -rw-r--r--   1  root     root     27576320 Mar 29  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.83.image
   208960  23832 -rwxr-xr-x   1  root     root     24401920 Feb 20  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.04.image
   208961     36 -rwxr-xr-x   1  root     root        33702 Apr  4  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/info.txt
   208962      0 drwxr-xr-x   1  root     root          416 Apr  2  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium
   208963  25532 -rw-r--r--   1  root     root     26142720 Mar 27  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.52.image
   208964      4 -rwxr-xr-x   1  root     root          291 Feb 11 21:12 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium/.listing
   208965  24540 -rwxr-xr-x   1  root     root     25128960 Oct 18  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.20.image
   208966  23840 -rwxr-xr-x   1  root     root     24412160 Jun 25  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.06.image
   208967  24612 -rw-r--r--   1  root     root     25200640 Feb 20  2016 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.31.image
   208968     24 -rwxr-xr-x   1  root     root        22050 Mar 27  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/belgium/info.txt
   208969      0 drwxr-xr-x   1  root     root          608 Apr  2  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch
   208970  25532 -rw-r--r--   1  root     root     26142720 May 26  2016 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.52.image
   208971  24612 -rwxr-xr-x   1  root     root     25200640 Aug 28  2015 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.30.image
   208972  26872 -rw-r--r--   1  root     root     27514880 Feb  3  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.80.image
   208973      4 -rwxr-xr-x   1  root     root          291 Feb 11 21:12 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/.listing
   208974  24540 -rwxr-xr-x   1  root     root     25128960 Oct 18  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.20.image
   208975  26932 -rw-r--r--   1  root     root     27576320 Mar 29  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.83.image
   208976  23832 -rwxr-xr-x   1  root     root     24401920 Feb 20  2014 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.04.image
   208977     52 -rwxr-xr-x   1  root     root        52890 Mar 29  2017 ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/deutsch_a-ch/info.txt

and if I try it myself (with 06.52, I haven't any 06.53 version), the results are:

vidar:/home/GitHub/YourFritz/eva_tools # tar tvf ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.52.image
drwxr-x--- 0/0               0 2016-05-25 11:58 ./var/
-r-xr-x--- 0/0          283844 2016-05-18 11:47 ./var/regelex
-rwxr-x--- 0/0           34069 2016-05-25 11:58 ./var/install
-rwxr-x--- 0/0            2795 2016-05-25 11:58 ./var/info.txt
drwxr-x--- 0/0               0 2016-05-25 11:58 ./var/tmp/
-rw-r----- 0/0        23027720 2016-05-25 11:58 ./var/tmp/filesystem.image
-rw-r----- 0/0         2507016 2016-05-25 11:58 ./var/tmp/kernel.image
-r-xr-x--- 0/0          278552 2016-05-18 11:47 ./var/chksum
-rw-r----- 0/0             128 2016-05-25 11:58 ./var/signature
vidar:/home/GitHub/YourFritz/eva_tools # image2ram < ../../../FritzBox/ftp.avm.de/fritz.box/fritzbox.7490/firmware/english/FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.52.image > 7490i_06.52.img
vidar:/home/GitHub/YourFritz/eva_tools # stat 7490i_06.52.img
  File: 7490i_06.52.img
  Size: 25534720        Blocks: 49880      IO Block: 4096   regular file
Device: 58h/88d Inode: 1049260     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2018-03-10 14:47:10.111022670 +0100
Modify: 2018-03-10 14:50:37.288123418 +0100
Change: 2018-03-10 14:50:37.288123418 +0100
 Birth: -
vidar:/home/GitHub/YourFritz/eva_tools # echo $(( 23027720 + 2507016 - 16 ))
25534720 => size is OK

Searching for "sqsh" leads to:

vidar:/home/GitHub/YourFritz/eva_tools # hexdump -C 7490i_06.52.img | grep -C 5 sqsh
00264030  2f 75 0f f2 ba e5 69 0a  3b e4 5d 49 a1 77 bd 17  |/u....i.;.]I.w..|
00264040  7b 5f 8d 7e 06 bd 1f b2  9d 28 d4 36 84 f3 c0 f4  |{_.~.....(.6....|
00264050  cd e0 17 9f cc 6c 00 00  00 00 30 78 00 80 00 00  |.....l....0x....|
00264060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00264100  73 71 73 68 00 00 00 00  00 00 00 00 00 00 00 00  |sqsh............|
00264110  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00264600  d8 00 00 00 d4 57 00 00  00 00 00 00 7d 07 00 00  |.....W......}...|
00264610  09 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  |................|
00264620  48 1d 00 00 48 1d 00 00  48 00 00 00 00 00 00 00  |H...H...H.......|
--
00f27a50  01 2f f7 b5 00 46 58 e8  01 2f f7 b6 00 46 58 f0  |./...FX../...FX.|
00f27a60  01 2f f7 b7 00 46 58 f8  00 01 19 54 00 46 58 fc  |./...FX....T.FX.|
00f27a70  01 2f d1 6d 00 46 59 00  53 46 54 4e 00 46 59 04  |./.m.FY.SFTN.FY.|
00f27a80  01 02 19 94 00 46 59 0c  52 65 49 73 00 46 59 14  |.....FY.ReIs.FY.|
00f27a90  28 cd 3d 45 00 46 59 20  00 00 72 75 00 46 59 28  |(.=E.FY ..ru.FY(|
00f27aa0  85 84 58 f6 00 46 59 28  73 71 73 68 00 46 59 30  |..X..FY(sqsh.FY0|
00f27ab0  62 65 65 72 00 46 59 3c  00 00 00 00 00 45 e2 74  |beer.FY<.....E.t|
00f27ac0  00 46 4b dc 00 46 6f ec  00 46 30 f0 00 46 74 e8  |.FK..Fo..F0..Ft.|
00f27ad0  00 00 00 00 00 44 73 75  00 44 73 75 00 40 cd 2d  |[email protected]|
00f27ae0  00 40 d9 11 00 42 f8 45  00 43 e8 f5 00 40 5b f1  |[email protected]...@[.|
00f27af0  00 43 4d 4d 00 43 4d 4d  00 43 71 91 00 43 ea 2d  |.CMM.CMM.Cq..C.-|
--
*
01114200  97 00 00 00 0c 00 01 00  2e 00 00 00 02 00 00 00  |................|
01114210  f4 03 02 00 2e 2e 00 00  00 00 00 00 00 00 00 00  |................|
01114220  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01114600  73 71 73 68 00 00 0d 36  01 2c f4 86 00 01 00 00  |sqsh...6.,......|
01114610  00 00 01 3e 00 04 00 10  02 c0 00 01 00 04 00 00  |...>............|
01114620  00 00 00 00 65 34 03 6a  00 00 00 00 01 2c f4 86  |....e4.j.....,..|
01114630  00 00 00 00 01 2c f4 7e  ff ff ff ff ff ff ff ff  |.....,.~........|
01114640  00 00 00 00 01 2b f6 56  00 00 00 00 01 2c 5d 08  |.....+.V.....,].|
01114650  00 00 00 00 01 2c da e4  00 00 00 00 01 2c f4 58  |.....,.......,.X|

and the offset for the SquashFS dummy header at 0x264100 is the next integral boundary after the kernel size:

vidar:/home/GitHub/YourFritz/eva_tools # printf "%08x\n" 2507016
00264108
vidar:/home/GitHub/YourFritz/eva_tools # printf "%08x\n" 25534720
0185a100

(after the checksum was truncated) and the overall size of the image (it's important, because the image is loaded from top to down into memory and the kernel has to start on a 256-byte boundary, too) looks also correct.

The second occurrence of "sqsh" is normal ... it's the "inner core filesystem image" and in an 'ext2' image (which follows the first "sqsh" dummy header), each file (block) starts at a 512-byte boundary (here at 0x1114200).

I've no more ideas ... probably you should check your source file(s) for a correct signature from AVM.

The keys from the international version (read from 06.83-intl) are the following:

vidar:/home/FritzBox/FB7490/firmware/113.06.83/etc # for f in avm_firmware_public_key*; do echo "$f"; cat "$f"; done
avm_firmware_public_key1
00cbdcfcc6ac9a1657a1c6f197e3056f1d68b8bb7deb480249e5f0ded677c54fde10be5a14b1e6a395483bd4bee608c09d385b1e90564ca84b9272926c45bfd328d7da876567e3e15f719800a53ecc21af583431d0c40806ca89f6f958e188ec69572df09e24de71eaa0782c01877158f286afd95037e7eb059367c466095944e1
010001
avm_firmware_public_key2
00c381540e8255baf78d29b7ac182e088cf8f2f4f418c186e927510cb469b5c16b6d161e6b0354c199d9721a5fda037047d4ec6f6e6bfc02ce5335023b24e757b7d8241e91f39fa43381b7b028ef65007e97593fe1b86d406767db7984fa7d780178ae2cfea9dc9ab7656692e643755397dd49ffdd2eb4abfc9cacc0bd6746fcdb
010001
avm_firmware_public_key3
00f2ee9ffd8556211f5644da48a252b107124b330d4c20dcf3b9bac892924cabaa4df4f53e1c62e3f2aa12a23eb1d770df1520a998078738407e6a71b077f73ba976363836b880b0dd88741bc3b83ab061691226e823404b7fc88ed278d8130fe5336eb925c78f2f8ad7cb87d9586286f768ab3236fa8fb51ae7c4bbe1e041d849
010001

You may use the tools from "signimage" directory to check the original signature.

 

[Pingwing]

I tried again to make the image file and it looks the same as the responses you showed me in the previous post (thank you for this)
The size is also exactly the same as mentioned above.

It looks a bit like this:

joris@jubuntu:/tmp$ hexdump -C ToTest.img | grep -C 5 sqsh
002640a0  f0 47 66 28 1d 87 bb 4e  01 85 e8 8a e1 6f 3a da  |.Gf(...N.....o:.|
002640b0  20 8c 3b 64 b5 d1 37 51  c1 76 1c 2d 9e 61 26 f3  | .;d..7Q.v.-.a&.|
002640c0  00 a4 cf cc 6c 00 00 00  00 30 78 00 80 00 00 00  |....l....0x.....|
002640d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00264100  73 71 73 68 00 00 00 00  00 00 00 00 00 00 00 00  |sqsh............|
00264110  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00264600  d8 00 00 00 d4 57 00 00  00 00 00 00 7d 07 00 00  |.....W......}...|
00264610  09 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  |................|
00264620  48 1d 00 00 48 1d 00 00  48 00 00 00 00 00 00 00  |H...H...H.......|
--
00f27a50  01 2f f7 b5 00 46 58 e8  01 2f f7 b6 00 46 58 f0  |./...FX../...FX.|
00f27a60  01 2f f7 b7 00 46 58 f8  00 01 19 54 00 46 58 fc  |./...FX....T.FX.|
00f27a70  01 2f d1 6d 00 46 59 00  53 46 54 4e 00 46 59 04  |./.m.FY.SFTN.FY.|
00f27a80  01 02 19 94 00 46 59 0c  52 65 49 73 00 46 59 14  |.....FY.ReIs.FY.|
00f27a90  28 cd 3d 45 00 46 59 20  00 00 72 75 00 46 59 28  |(.=E.FY ..ru.FY(|
00f27aa0  85 84 58 f6 00 46 59 28  73 71 73 68 00 46 59 30  |..X..FY(sqsh.FY0|
00f27ab0  62 65 65 72 00 46 59 3c  00 00 00 00 00 45 e2 74  |beer.FY<.....E.t|
00f27ac0  00 46 4b dc 00 46 6f ec  00 46 30 f0 00 46 74 e8  |.FK..Fo..F0..Ft.|
00f27ad0  00 00 00 00 00 44 73 75  00 44 73 75 00 40 cd 2d  |[email protected]|
00f27ae0  00 40 d9 11 00 42 f8 45  00 43 e8 f5 00 40 5b f1  |[email protected]...@[.|
00f27af0  00 43 4d 4d 00 43 4d 4d  00 43 71 91 00 43 ea 2d  |.CMM.CMM.Cq..C.-|
--
*
01114200  97 00 00 00 0c 00 01 00  2e 00 00 00 02 00 00 00  |................|
01114210  f4 03 02 00 2e 2e 00 00  00 00 00 00 00 00 00 00  |................|
01114220  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01114600  73 71 73 68 00 00 0d 36  01 2c fe 5e 00 01 00 00  |sqsh...6.,.^....|
01114610  00 00 01 3e 00 04 00 10  02 c0 00 01 00 04 00 00  |...>............|
01114620  00 00 00 00 67 54 03 6a  00 00 00 00 01 2c fe 5e  |....gT.j.....,.^|
01114630  00 00 00 00 01 2c fe 56  ff ff ff ff ff ff ff ff  |.....,.V........|
01114640  00 00 00 00 01 2b fd ca  00 00 00 00 01 2c 66 9c  |.....+.......,f.|
01114650  00 00 00 00 01 2c e4 a4  00 00 00 00 01 2c fe 30  |.....,.......,.0|
joris@jubuntu:/tmp$ printf "%08x\n" 2507016
00264108
joris@jubuntu:/tmp$ printf "%08x\n" 25534720
0185a100

As input I used the latest firmware , found on the AVM ftp server. So I guess it should be fine.

Still when I try to upload the image. I get the same response.
So my hardware in the end?
I also wondered after the RebootTheDevice script, what is the expected behavior from the FB? Because mine just reboots and then the info led flashes again. (3sec nothing and then 2 flashes)

 

[Micha0815]

I remember poorly, that another Member here @stoney have had a similiar problem to push up with the scripts in binary-mode to a FB6490. The result/Guilty was iirc the Chipset of the NIC of the Client-PC?
So if possible test another Client-PC with another Chipset of LAN.
LG

 

[Pingwing]

Hi @Micha0815 , Thank you for helping a hand. I've already tried the following setups:

With the recoveryprogram:
- Windows PC directly connected to the FB
- Windows PC to switch. Switch to FB.
- Ubuntu (wine) laptop directly connected to the FB
- Ubuntu laptop to switch. Switch to FB

With the sripts and powershell:
- Windows PC directly connected to the FB
- Windows PC to switch. Switch to FB.

None of them with a satisfying result. I'm afraid the FB is more or less death? :-(

 

[stoney]

I think @Micha0815 means this thread
https://www.ip-phone-forum.de/threa...gen-und-ändern-der-bootpartition-6490.289201/
The problem still the same, but I dont think the problem is on clientside

I've testet it on to different machines.
The first one are Ubuntu 16.04 (installed)
The second was freetzVM

At leaste I split the file(s) and uploaded one for one.

when I have time and desire, I will test it with a raspberry or/and a bananapi

 

[Pingwing]

Where you successfull in the end? I would already be very happy if I could upload something. It's like the FB is blocking everything. Will this uploading in smaller pieces work for the 7490 as well?

 

[stoney]

I had no success so far thats the reason why is wrote about the Pi"s.
but I do not believe it

 

[Micha0815]

Sorry @Pingwing if a failed in remembering and @stoney
In quicksearch I can`t find the Topic. But as I remember correctly, it was a problem found over wireshark while uploading via the script image2ram where in the deep debug the speed from Client-Lan to FB6490 was to fast (Blocksize?) while uploading/writing @mtd-x ... mtd-y in serial-mode via adam2-ftp.

@#33 mentioned Ubuntu-Laptop ... Intel-NIC? Something elder with Broadcom-HW possible?
But may be a realy non-relevant hint from myside.
LG

Edit: Sorry that I missed the nomenclature of bootloader and urloader which are kongruent in the last 3 digits behind the significant point e.g
Bootloader 1.1777->Urlader 2777 btw. HW-Subrevision 3
Bootloader 1.1964->Urlader 2964 btw. HW-Subrevision 6
Bootloader 1.3179->Urlader 4179 btw. HW-Subrevision 7
Just the last combination, known with branding-switch-problems may be interested?

 

[PeterPawn]

@Pingwing:
OK, now your image looks good ... do you know meanwhile, what the earlier problem was?

If it still refuses to boot with this image, the next possible explanation would be an error during transmission.

You should try to get a complete packet dump of the upload ... then you may use 'Wireshark' to analyze the FTP-DATA connection and extract the raw transmitted data. It should reassemble data to the same size and content as your source image for the upload.

And as a bonus, it would show any errors related to the TCP flow control - even if I don't believe, that there's a problem.

The last idea regarding this error would be a defective RAM of the device ... if EVA can't expand the compressed kernel in memory (because there's an error at the place, where the kernel was stored during upload), I would expect the same error (553).

Here a try with another "load origin" could be the solution ... this can be achieved by adding some dummy blocks (with the size of your image, rounded up to the next 4K boundary) at the end of the image. It simply shifts the position of the kernel downwards in memory.

You may use this command to produce such a "double-sized" image:

cat 7490i_06.52.img.saved /dev/zero | dd bs=4096 count=$(( ( $(stat -c %s 7490i_06.52.img) * 2 / 4096 ) + 1 )) of=7490.img2 conv=sync

The filenames have to be adapted to your real names ... the command above produces an image of the double size from the first file, filled with binary zeros.

After all these tries I don't have any further ideas, why your bootloader doesn't accept any images ... you may double-check this problem by a packet dump of the communication between the recovery program and the device.

At the end, the recovery program uses the same command sequence and the same upload format - if here the answer is a "553" too, the reason for the (a bit unspecific) error message from the recovery program was found. But that's no answer, why EVA refuses to load and start such images.

 

[Pingwing]

@PeterPawn :
Thanks for your help again. I've made the image bigger like you said, but unfortunately without prevail.

PS C:\7490\YourFritz-master\eva_tools> .\EVA-Discover.ps1 -maxWait 120 -Debug -Verbose
VERBOSE: Sending discovery packet (1) ...
DEBUG: Received UDP packet from 192.168.178.1:5035 ...
VERBOSE: Trying to connect to the FTP port to hold up the device in bootloader ...
DEBUG: Error during FTP connection attempt ...
EVA_IP=192.168.178.1
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { SwitchSystem }
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { RebootTheDevice }
True
PS C:\7490\YourFritz-master\eva_tools> .\EVA-FTP-Client.ps1 -ScriptBlock { BootDeviceFromImage 7490.img2 } -Debug -Verbo
se
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.1964 0x0 0x740D

================
DEBUG: Sent
GETENV memsize
================
DEBUG: Response:
memsize               0x10000000

200 GETENV command successful

================
DEBUG: Memory size found    : 08000000
DEBUG: Image size found     : 0x030b5000
DEBUG: Set memory size to   : 0x04f4b000
DEBUG: Set MTD ram device to: 0x84f4b000,0x88000000
DEBUG: Sent
SETENV memsize 0x04f4b000
================
DEBUG: Response:
200 SETENV command successful

================
DEBUG: Sent
SETENV kernel_args_tmp mtdram1=0x84f4b000,0x88000000
================
DEBUG: Response:
200 SETENV command successful

================
DEBUG: Sent
TYPE I
================
DEBUG: Response:
200 Type set to BINARY

================
DEBUG: Sent
MEDIA SDRAM
================
DEBUG: Response:
200 Media set to MEDIA_SDRAM

================
DEBUG: Uploading file '7490.img2' to '0x84f4b000 0x88000000' ...
DEBUG: Sent
P@SW
================
DEBUG: Response:
227 Entering Passive Mode (192,168,178,1,12,10)

================
DEBUG: Sent
STOR 0x84f4b000 0x88000000
================
DEBUG: Response:
150 Opening BINARY data connection

================
DEBUG: Response:
553 Execution failed.

================
DEBUG: Sent
SETENV memsize 0x0x10000000
================
DEBUG: Response:
200 SETENV command successful

================
DEBUG: Sent
UNSETENV kernel_args_tmp
================
DEBUG: Response:
501 environment variable not set

================
DEBUG: Sent
QUIT
================
DEBUG: Response:
221 Thank you for using the FTP service on ADAM2
221 Goodbye.

================
Exception calling "Invoke" with "0" argument(s): "Error uploading image file."
At C:\7490\YourFritz-master\eva_tools\EVA-FTP-Client.ps1:627 char:21
+                     $ScriptBlock.Invoke()
+                     ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

The last thing to do is to check with the 'Wireshark', but since this again something new, I leave it for this evening. My wife starts to wonder what I'm doing here all the time.

UPDATE:
So I've used Whireshark while I was trying to upload the image of aprox 25MB made with Image2ram but I don' know where to look exactly, maybe you could help.

Here are some outputs:

No.     Time           Source                Destination           Protocol Length Info
     49 1.165270       192.168.178.1         192.168.178.2         FTP      102    Response: 227 Entering Passive Mode (192,168,178,1,12,2)

Frame 49: 102 bytes on wire (816 bits), 102 bytes captured (816 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 323, Ack: 155, Len: 48
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
     50 1.208087       192.168.178.2         192.168.178.1         TCP      54     16185 → 21 [ACK] Seq=155 Ack=371 Win=63870 Len=0

Frame 50: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 155, Ack: 371, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     51 1.208331       192.168.178.1         192.168.178.2         TCP      60     [TCP Window Update] 21 → 16185 [ACK] Seq=371 Ack=155 Win=28800 Len=0

Frame 51: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 371, Ack: 155, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     52 1.300439       192.168.178.2         192.168.178.1         TCP      66     16186 → 3074 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1

Frame 52: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 0, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     53 1.300743       192.168.178.1         192.168.178.2         TCP      60     3074 → 16186 [SYN, ACK] Seq=0 Ack=1 Win=28800 Len=0 MSS=1440

Frame 53: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 3074, Dst Port: 16186, Seq: 0, Ack: 1, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     54 1.300948       192.168.178.2         192.168.178.1         TCP      54     16186 → 3074 [ACK] Seq=1 Ack=1 Win=64240 Len=0

Frame 54: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 1, Ack: 1, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     55 1.303037       192.168.178.2         192.168.178.1         FTP      82     Request: STOR 0x867a5f00 0x88000000

Frame 55: 82 bytes on wire (656 bits), 82 bytes captured (656 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 155, Ack: 371, Len: 28
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
     56 1.303314       192.168.178.1         192.168.178.2         TCP      60     21 → 16185 [PSH, ACK] Seq=371 Ack=183 Win=28772 Len=0

Frame 56: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 371, Ack: 183, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     57 1.303316       192.168.178.1         192.168.178.2         FTP      90     Response: 150 Opening BINARY data connection

Frame 57: 90 bytes on wire (720 bits), 90 bytes captured (720 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 371, Ack: 183, Len: 36
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
     58 1.348084       192.168.178.2         192.168.178.1         TCP      54     16185 → 21 [ACK] Seq=183 Ack=407 Win=63834 Len=0

Frame 58: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 183, Ack: 407, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     59 1.348330       192.168.178.1         192.168.178.2         TCP      60     [TCP Dup ACK 56#1] 21 → 16185 [ACK] Seq=407 Ack=183 Win=28800 Len=0

Frame 59: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 407, Ack: 183, Len: 0

No.     Time           Source                Destination           Protocol Length Info
     60 1.472616       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 60: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 1, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

After package 60 I see a continuous stream of the same packages all the time up to package 18727
Such an attempt (I think it is) looks like:

No.     Time           Source                Destination           Protocol Length Info
     71 1.479639       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 71: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 14401, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     72 1.479651       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 72: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 15841, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     73 1.479666       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 73: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 17281, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     74 1.479672       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 74: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 18721, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     75 1.479679       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 75: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 20161, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     76 1.479685       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 76: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 21601, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     77 1.479691       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 77: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 23041, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     78 1.479698       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 78: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 24481, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     79 1.479705       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 79: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 25921, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     80 1.479713       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 80: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 27361, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     81 1.479719       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 81: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 28801, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     82 1.479726       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 82: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 30241, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     83 1.479734       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 83: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 31681, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     84 1.479740       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 84: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 33121, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     85 1.479747       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 85: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 34561, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     86 1.479754       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 86: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 36001, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     87 1.479760       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 87: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 37441, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     88 1.479767       192.168.178.2         192.168.178.1         FTP-DATA 1494   FTP Data: 1440 bytes

Frame 88: 1494 bytes on wire (11952 bits), 1494 bytes captured (11952 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 38881, Ack: 1, Len: 1440
FTP Data (1440 bytes data)

No.     Time           Source                Destination           Protocol Length Info
     89 1.487551       192.168.178.1         192.168.178.2         TCP      60     3074 → 16186 [ACK] Seq=1 Ack=40321 Win=28800 Len=0

Frame 89: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 3074, Dst Port: 16186, Seq: 1, Ack: 40321, Len: 0

In the end it stops with these package's:

No.     Time           Source                Destination           Protocol Length Info
  18728 7.405190       192.168.178.1         192.168.178.2         TCP      60     3074 → 16186 [ACK] Seq=1 Ack=25534081 Win=28800 Len=0

Frame 18728: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 3074, Dst Port: 16186, Seq: 1, Ack: 25534081, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18729 7.405251       192.168.178.2         192.168.178.1         FTP-DATA 694    FTP Data: 640 bytes

Frame 18729: 694 bytes on wire (5552 bits), 694 bytes captured (5552 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 25534081, Ack: 1, Len: 640
FTP Data (640 bytes data)

No.     Time           Source                Destination           Protocol Length Info
  18730 7.405466       192.168.178.1         192.168.178.2         TCP      60     3074 → 16186 [PSH, ACK] Seq=1 Ack=25534721 Win=28160 Len=0

Frame 18730: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 3074, Dst Port: 16186, Seq: 1, Ack: 25534721, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18731 7.478778       192.168.178.2         192.168.178.1         TCP      54     16186 → 3074 [FIN, ACK] Seq=25534721 Ack=1 Win=64240 Len=0

Frame 18731: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 25534721, Ack: 1, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18732 7.479026       192.168.178.1         192.168.178.2         TCP      60     [TCP Window Update] 3074 → 16186 [ACK] Seq=1 Ack=25534721 Win=28800 Len=0

Frame 18732: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 3074, Dst Port: 16186, Seq: 1, Ack: 25534721, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18733 7.479027       192.168.178.1         192.168.178.2         TCP      60     3074 → 16186 [FIN, ACK] Seq=1 Ack=25534722 Win=28800 Len=0

Frame 18733: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 3074, Dst Port: 16186, Seq: 1, Ack: 25534722, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18734 7.479094       192.168.178.2         192.168.178.1         TCP      54     16186 → 3074 [ACK] Seq=25534722 Ack=2 Win=64240 Len=0

Frame 18734: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16186, Dst Port: 3074, Seq: 25534722, Ack: 2, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18735 9.347090       192.168.178.1         192.168.178.2         FTP      77     Response: 553 Execution failed.

Frame 18735: 77 bytes on wire (616 bits), 77 bytes captured (616 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 407, Ack: 183, Len: 23
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
  18736 9.388103       192.168.178.2         192.168.178.1         TCP      54     16185 → 21 [ACK] Seq=183 Ack=430 Win=63811 Len=0

Frame 18736: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 183, Ack: 430, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18737 9.388335       192.168.178.1         192.168.178.2         TCP      60     [TCP Dup ACK 56#2] 21 → 16185 [ACK] Seq=430 Ack=183 Win=28800 Len=0

Frame 18737: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 430, Ack: 183, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18738 12.597310      192.168.178.2         192.168.178.1         FTP      83     Request: SETENV memsize 0x0x10000000

Frame 18738: 83 bytes on wire (664 bits), 83 bytes captured (664 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 183, Ack: 430, Len: 29
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
  18739 12.600304      192.168.178.1         192.168.178.2         TCP      60     21 → 16185 [PSH, ACK] Seq=430 Ack=212 Win=28771 Len=0

Frame 18739: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 430, Ack: 212, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18740 12.600305      192.168.178.1         192.168.178.2         FTP      85     Response: 200 SETENV command successful

Frame 18740: 85 bytes on wire (680 bits), 85 bytes captured (680 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 430, Ack: 212, Len: 31
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
  18741 12.648102      192.168.178.2         192.168.178.1         TCP      54     16185 → 21 [ACK] Seq=212 Ack=461 Win=63780 Len=0

Frame 18741: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 212, Ack: 461, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18742 12.648337      192.168.178.1         192.168.178.2         TCP      60     [TCP Window Update] 21 → 16185 [ACK] Seq=461 Ack=212 Win=28800 Len=0

Frame 18742: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 461, Ack: 212, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18743 12.702111      192.168.178.2         192.168.178.1         FTP      80     Request: UNSETENV kernel_args_tmp

Frame 18743: 80 bytes on wire (640 bits), 80 bytes captured (640 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 212, Ack: 461, Len: 26
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
  18744 12.702334      192.168.178.1         192.168.178.2         TCP      60     21 → 16185 [PSH, ACK] Seq=461 Ack=238 Win=28774 Len=0

Frame 18744: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 461, Ack: 238, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18745 12.702335      192.168.178.1         192.168.178.2         FTP      88     Response: 501 environment variable not set

Frame 18745: 88 bytes on wire (704 bits), 88 bytes captured (704 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 461, Ack: 238, Len: 34
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
  18746 12.758098      192.168.178.2         192.168.178.1         TCP      54     16185 → 21 [ACK] Seq=238 Ack=495 Win=63746 Len=0

Frame 18746: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 238, Ack: 495, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18747 12.758349      192.168.178.1         192.168.178.2         TCP      60     [TCP Window Update] 21 → 16185 [ACK] Seq=495 Ack=238 Win=28800 Len=0

Frame 18747: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 495, Ack: 238, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18748 12.823239      192.168.178.2         192.168.178.1         FTP      60     Request: QUIT

Frame 18748: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AsustekC_56:4e:7d (c8:60:00:56:4e:7d), Dst: AvmAudio_2a:03:99 (38:10:d5:2a:03:99)
Internet Protocol Version 4, Src: 192.168.178.2, Dst: 192.168.178.1
Transmission Control Protocol, Src Port: 16185, Dst Port: 21, Seq: 238, Ack: 495, Len: 6
File Transfer Protocol (FTP)

No.     Time           Source                Destination           Protocol Length Info
  18749 12.823490      192.168.178.1         192.168.178.2         TCP      60     21 → 16185 [PSH, ACK] Seq=495 Ack=244 Win=28794 Len=0

Frame 18749: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 495, Ack: 244, Len: 0

No.     Time           Source                Destination           Protocol Length Info
  18750 12.823491      192.168.178.1         192.168.178.2         FTP      118    Response: 221 Thank you for using the FTP service on ADAM2

Frame 18750: 118 bytes on wire (944 bits), 118 bytes captured (944 bits) on interface 0
Ethernet II, Src: AvmAudio_2a:03:99 (38:10:d5:2a:03:99), Dst: AsustekC_56:4e:7d (c8:60:00:56:4e:7d)
Internet Protocol Version 4, Src: 192.168.178.1, Dst: 192.168.178.2
Transmission Control Protocol, Src Port: 21, Dst Port: 16185, Seq: 495, Ack: 244, Len: 64
File Transfer Protocol (FTP)

Where do I need to place my focus to find the mistake? Because I'm struggling to read this data.

 

[PeterPawn]

I did a test with an image for 113.06.53 (belgium) myself, after I found this version on AVM's FTP server.

The used image "7490.img" was created exactly as shown above and I've got the following outcomes:

vidar:/home/GitHub/YourFritz/eva_tools # ./eva_to_memory 7490.img 192.168.xxx.1
Found AVM bootloader: AVM EVA Version 1.1964 0x0 0x740D
Found hardware revision: 185
Memory size is 0x10000000 (256 MB)
Memory size limited to 128 MB
Image size is 0x185a100 (24 MB)
Setting temporary memory size to: 0x067a5f00
Setting temporary kernel args to: mtdram1=0x867a5f00,0x88000000
Image uploaded to device.
vidar:/home/GitHub/YourFritz/eva_tools # cat eva_to_memory.log
220 ADAM2 FTP Server ready
USER adam2
331 Password required for adam2
PASS adam2
230 User adam2 successfully logged in
SYST
215 AVM EVA Version 1.1964 0x0 0x740D
TYPE I
200 Type set to BINARY
MEDIA SDRAM
200 Media set to MEDIA_SDRAM
P@SW
227 Entering Passive Mode (192,168,xxx,1,12,0)
RETR env
150 Opening BINARY data connection
226 Transfer complete
SETENV memsize 0x067a5f00
200 SETENV command successful
SETENV kernel_args_tmp mtdram1=0x867a5f00,0x88000000
200 SETENV command successful
TYPE I
200 Type set to BINARY
MEDIA SDRAM
200 Media set to MEDIA_SDRAM
P@SW
227 Entering Passive Mode (192,168,xxx,1,12,0)
STOR 0x867a5f00 0x88000000
150 Opening BINARY data connection
226 Transfer complete
vidar:/home/GitHub/YourFritz/eva_tools # sha256sum 7490.img
d1a67d12df4c3b38d3375a4905e60a552b3f0ea183fc4e494325dee953d989d3  7490.img
vidar:/home/GitHub/YourFritz/eva_tools #

After I had switched the branding (firmware_version) to "avme", the device didn't hesitate to boot with the new version:

After switching back to "avm", I've restarted once again and checked, that the correct version was installed in the alternative partitions:

My summary: The problem should not be related to the used image, as far as your own image has the same SHA-256 hash value as shown above.

If you use "Wireshark" to analyze the packet dump, it should offer you a menu item (e.g. in the context menu of any data packet related to the FTP data connection) to "Follow TCP stream" - it filters only the packets from this connection and looks like this:

(I've used "Wireshark Legacy" here, because the newer version had some problems to assemble more than 11.000 packets)

A very first glance at the overall length of data -> it should be the same value as the size of your image file.

Using the "Save as ..." button you may create a copy (check, that "raw" format is selected) of transmitted data ... if you compare this file with your image (byte by byte as binary), there should be no difference.