Trying to flash Freetz-NG onto the FritzBox 7590: Connection and Flashing Issues #951

TechTune-1 · 2024-02-10T15:47:28Z

TechTune-1
Feb 10, 2024

I'm attempting to flash Freetz-NG onto my FritzBox 7590 router. After executing tools/push_firmware in the terminal and rebooting the FritzBox via http://192.168.178.1/#reboot, I encountered the following terminal output:

$ cd freetz-ng/

$ ftp ftp://fritz6037:[password]@192.168.178.1
Connected to 192.168.178.1.
220 FTP server ready.
331 Password required for fritz6037.
230 User fritz6037 logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Type set to I.
ftp> exit
221 Goodbye.

$ tools/push_firmware -mr

 * Product: Fritz_Box_HW226 (FRITZ!Box 7590)
 * Using command: ftp
 * Target host: 192.168.178.1
 * Outgoing IP: 192.168.178.20
 * Flash mode: ram-boot
 * Allowed memory size: 128 MB
 * Designated linux_fs_start: <other>

 !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!!
 !!!  THERE IS NO WARRANTY AT ALL !!! USE AT YOUR OWN RISK   !!!

 * Are you sure you want to flash this file to the device?
   images/7590_07.57.all_freetz-ng-23167-866f568de_20240208-151316.image
   Proceed? (y/[n]) y

 * You should now reboot your box (192.168.178.1). Waiting for shut down.
   Switch off if reboot is not detected because it happens too quickly.
   Some newer bootloader versions allow flashing on power-cycle only.
   ........................................................................................................................................................................
 * MAPSTART=0x80000000
 * FULLSIZE=0x08000000    (128 MB)
 * MAPLIMIT=0x88000000
 * FILESIZE=0x024e2f00    (~36 MB)
 * ALIBYTES=0x00000000    (~0 kB)
 * FREESIZE=0x05b1d100    (~91 MB)
 * MTDSTART=0x85b1d100

 * No reply from the box, assuming switch-off or restart. Trying to re-detect the box.
   Waiting .................................................. found!

ftp: Can't connect to `192.168.178.1:21': Connection refused
ftp: Can't connect to `192.168.178.1:ftp'
 * Detected linux_fs_start: '<unset>'
 * Designated linux_fs_start: 1

 * No reply from the box, assuming switch-off or restart. Trying to re-detect the box.
   Waiting . found!

 * Box is back up again, initiating transfer.

ftp: Can't connect to `192.168.178.1:21': Connection refused
ftp: Can't connect to `192.168.178.1:ftp'
Not connected.
Debugging on (debug=1).
Not connected.
Not connected.
Not connected.
Not connected.
Not connected.
Not connected.

done

As you can see, I'm able to connect to the router via FTP, but the flashing process fails. I suspect I can only flash when connected via FTP during the bootloader phase. I attempted to reboot the router by unplugging and reconnecting the power cord, but the progress halts with the message "No reply from box, assuming switch-off or restart." Rebooting multiple times only maintains the process at 0%. Additionally, I tried uploading the image file via http://192.168.178.1/#userUp, but upon clicking "start updating," I received the error:

FRITZ!Box Update
The update failed.
The specified file does not contain a FRITZ!OS released for this device by AVM.
The versions of FRITZ!OS released for your FRITZ!Box are:
* generated and publicized by AVM
* created for your FRITZ!Box model.

I'm seeking support on how to proceed from here. Thank you.

Conan179 · 2024-02-10T15:53:27Z

Conan179
Feb 10, 2024

Hast du es nur per reboot probiert oder auch richtig mit Stromstecker raus, kurz warten und dann wieder rein?

1 reply

TechTune-1 Feb 10, 2024
Author

Yes, I also attempted to restart the Fritzbox by power-plugging it out and then back in. When I noticed the message "No reply from box, assuming switch-off or restart. Trying to re-detect box" indicating it might not be in bootloader mode anymore, I re-plugged the Fritzbox. However, despite that, I encountered the same issue with the flashing process with the output being:

$ cd freetz-ng/

$ tools/push_firmware

 * Analyzing 'images/7590_07.57.all_freetz-ng-23167-866f568de_20240210-114200.image' ... 
 * Product: Fritz_Box_HW226 (FRITZ!Box 7590)
 * Using command: ftp
 * Target host: 192.168.178.1
 * Outgoing IP: 192.168.178.3
 * Flash mode: ram-boot
 * Allowed memory size: 128 MB
 * Designated linux_fs_start: <other>

 !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!!
 !!!  THERE IS NO WARRANTY AT ALL !!! USE AT YOUR OWN RISK   !!!

 * Are you sure, that you want to flash this file to the device?
   images/7590_07.57.all_freetz-ng-23167-866f568de_20240210-114200.image
   Proceed? (y/[n]) y

 * You should now reboot your box (192.168.178.1). Waiting for shut down.
   Switch off, if reboot is not detected because it happens too quickly.
   Some newer bootloader versions allow to flash on power-cycle only.
   ...................................................................................................
 * MAPSTART=0x80000000
 * FULLSIZE=0x08000000	(128 MB)
 * MAPLIMIT=0x88000000
 * FILESIZE=0x02f8df00	(~47 MB)
 * ALIBYTES=0x00000000	(~0 kB)
 * FREESIZE=0x05072100	(~80 MB)
 * MTDSTART=0x85072100

 * No reply from box, assuming switch-off or restart. Trying to re-detect box.
   Waiting ................... found!

 * Detected linux_fs_start: '0'
 * Designated linux_fs_start: 1

 * No reply from box, assuming switch-off or restart. Trying to re-detect box.
   Waiting ..................................................... found!

 * Box is back up again, initiating transfer.

Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
331 Password required for adam2
230 User adam2 successfully logged in
Remote system type is AVM.
Debugging on (debug=1).
---> TYPE I
200 Type set to BINARY
---> MEDIA SDRAM
200 Media set to MEDIA_SDRAM
---> SETENV memsize 0x05072100
200 SETENV command successful
---> SETENV kernel_args_tmp mtdram1=0x85072100,0x88000000
200 SETENV command successful
local: /tmp/freetz_aL8/ramboot.flash remote: 0x85072100 0x88000000
ftp: setsockopt SO_DEBUG (ignored): Permission denied
---> EPSV
502 Command not implemented
disabling epsv4 for this connection
---> PASV
227 Entering Passive Mode (192,168,178,1,12,16)
---> STOR 0x85072100 0x88000000
150 Opening BINARY data connection
  1% |*                                                                                                                                                   |   800 KiB    9.87 KiB/s  - stalled -ftp: Writing to network: Connection reset by peer
  0% |                                                                                                                                                    |    -1        0.00 KiB/s    --:-- ETA
421 Service not available, remote server timed out. Connection closed.
Not connected.

done

Would you have any further suggestions?

fda77 · 2024-02-10T18:40:27Z

fda77
Feb 10, 2024
Collaborator

You could try tools/push_firmware-experimental. Its not done yet but should work with your devide .. maybe. It reduces the reboot to only 1 instead of 3
And yes, 1st flash is only possible by bootloader

5 replies

TechTune-1 Feb 11, 2024
Author

Thank you for the suggestion. I've tried tools/push_firmware_experimental, and the updated output is as follows:

$ tools/push_firmware_experimental

 * Analyzing 'images/7590_07.57.all_freetz-ng-23167-866f568de_20240210-114200.image' ...
 * Product: Fritz_Box_HW226 (FRITZ!Box 7590)
 * Using dos2unix binary: tools/dos2unix
 * Using tar binary: tools/tar-gnu
 * Using ftp binary: tools/ftp
 * Target host: 192.168.178.1
 * Outgoing IP: 192.168.178.3
 * Flash mode: ram-boot
 * Allowed memory size: 208 MB
 * Designated linux_fs_start: <other>

 !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!!
 !!!  THERE IS NO WARRANTY AT ALL !!! USE AT YOUR OWN RISK   !!!

 * Are you sure, that you want to flash this file to the device?
   images/7590_07.57.all_freetz-ng-23167-866f568de_20240210-114200.image
   Proceed? (y/[n]) y

 * You should now reboot your box (192.168.178.1). Waiting for shut down.
   Switch off, if reboot is not detected because it happens too quickly.
   Some newer bootloader versions allow to flash on power-cycle only.
   ......................................................................................................................
 * No reply from box, assuming switch-off or restart. Trying to re-detect box.
   Waiting .................... found!

 * Reading 'env' file to /tmp/freetz_env_F12
   ProductID:         Fritz_Box_HW226
   SerialNumber:      P24464560040065
   HWRevision:        226
   HWSubRevision:     6
   memsize:           0x08000000
   linux_fs_start:    0

You are not connected to the bootloader of the device.

However, it seems that I'm still encountering an issue, as the output indicates: "You are not connected to the bootloader of the device."

Do you have any further suggestions or insights on how to proceed?

fda77 Feb 11, 2024
Collaborator

Thats a bug of the (not yet finished) scrpt. Just remove the line with the "not connected to the bootloader" error message

TechTune-1 Feb 11, 2024
Author

After removing the line containing "not connected to the bootloader," I reran tools/push_firmware_experimental. However, despite the update message upon logging into 192.168.178.1, the Freetz interface was not accessible. When attempting to access fritz.box:81, the browser returned "Unable to connect."

$ tools/push_firmware_experimental

 * Analyzing 'images/7590_07.57.all_freetz-ng-23167-866f568de_20240210-114200.image' ...
 * Product: Fritz_Box_HW226 (FRITZ!Box 7590)
 * Using dos2unix binary: tools/dos2unix
 * Using tar binary: tools/tar-gnu
 * Using ftp binary: tools/ftp
 * Target host: 192.168.178.1
 * Outgoing IP: 192.168.178.3
 * Flash mode: ram-boot
 * Allowed memory size: 208 MB
 * Designated linux_fs_start: <other>

 !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!!
 !!!  THERE IS NO WARRANTY AT ALL !!! USE AT YOUR OWN RISK   !!!

 * Are you sure, that you want to flash this file to the device?
   images/7590_07.57.all_freetz-ng-23167-866f568de_20240210-114200.image
   Proceed? (y/[n]) y

 * You should now reboot your box (192.168.178.1). Waiting for shut down.
   Switch off, if reboot is not detected because it happens too quickly.
   Some newer bootloader versions allow to flash on power-cycle only.
   .....................................................................................................
 * No reply from box, assuming switch-off or restart. Trying to re-detect box.
   Waiting ................. found!

 * Reading 'env' file to /tmp/freetz_env_8If
   ProductID:          Fritz_Box_HW226
   HWRevision:         226
   HWSubRevision:      6
   memsize:            0x08000000
   linux_fs_start:     0

 * MAPSTART=0x80000000
 * FULLSIZE=0x0D000000    (208 MB)
 * MAPLIMIT=0x8d000000
 * FILESIZE=0x02f8df00    (~47 MB)
 * ALIBYTES=0x00000000    (~0 kB)
 * FREESIZE=0x0a072100    (~160 MB)
 * MTDSTART=0x8a072100

 * Detected linux_fs_start: '0'
 * Designated linux_fs_start: 1

 * Box is back up again, initiating transfer.

Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
331 Password required for adam2
230 User adam2 successfully logged in
Remote system type is AVM.
Debugging on (debug=1).
---> TYPE I
200 Type set to BINARY
---> MEDIA SDRAM
200 Media set to MEDIA_SDRAM
---> SETENV memsize 0x0a072100
200 SETENV command successful
---> SETENV kernel_args_tmp mtdram1=0x8a072100,0x8d000000
200 SETENV command successful
local: /tmp/freetz_BE3/ramboot.flash remote: 0x8a072100 0x8d000000
---> PASV
227 Entering Passive Mode (192,168,178,1,12,22)
---> STOR 0x8a072100 0x8d000000
150 Opening BINARY data connection
226 Transfer complete
49864448 bytes sent in 9.66 secs (4.9233 MB/s)
---> SETENV linux_fs_start 1
200 SETENV command successful
---> QUIT
221 Thank you for using the FTP service on ADAM2

done

Any further suggestions on how to proceed would be greatly appreciated. Thank you!

fda77 Feb 11, 2024
Collaborator

I see no error, should work!
Each time after a successfully flash, the "linux_fs_start" should toggle between 1 and 0

TechTune-1 Feb 11, 2024
Author

The Fritzbox Event Log
indicates that the service provider has updated the firmware, as evidenced by the provided image.

fda77 · 2024-02-11T17:01:02Z

fda77
Feb 11, 2024
Collaborator

The provider did this instantly after you flashed freetz? Was Freetz with Fos 7.56 or 7.57 ?
You could remove

Remove public firmware key
Remove tr069

to try to stop your provider from doing this :)

1 reply

TechTune-1 Feb 13, 2024
Author

Yes, it appears that the provider updated the firmware immediately after the Freetz flashing. Initially, Freetz was on 7.57, but sometimes, it also reverts to 7.56 for unknown reasons. Removing TR-069 alone did not prevent the update.

Regarding the removal of the public firmware key, could you provide guidance on how to do this? Thank you!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Trying to flash Freetz-NG onto the FritzBox 7590: Connection and Flashing Issues #951

{{title}}

Replies: 3 comments 7 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Trying to flash Freetz-NG onto the FritzBox 7590: Connection and Flashing Issues #951

TechTune-1 Feb 10, 2024

Replies: 3 comments · 7 replies

Conan179 Feb 10, 2024

TechTune-1 Feb 10, 2024 Author

fda77 Feb 10, 2024 Collaborator

TechTune-1 Feb 11, 2024 Author

fda77 Feb 11, 2024 Collaborator

TechTune-1 Feb 11, 2024 Author

fda77 Feb 11, 2024 Collaborator

TechTune-1 Feb 11, 2024 Author

fda77 Feb 11, 2024 Collaborator

TechTune-1 Feb 13, 2024 Author

TechTune-1
Feb 10, 2024

Replies: 3 comments 7 replies

Conan179
Feb 10, 2024

TechTune-1 Feb 10, 2024
Author

fda77
Feb 10, 2024
Collaborator

TechTune-1 Feb 11, 2024
Author

fda77 Feb 11, 2024
Collaborator

TechTune-1 Feb 11, 2024
Author

fda77 Feb 11, 2024
Collaborator

TechTune-1 Feb 11, 2024
Author

fda77
Feb 11, 2024
Collaborator

TechTune-1 Feb 13, 2024
Author