Reinstall 21.02 on Fritz!Repeater 3000

[GqSteve]

Hi,

I installed 21.02 successfully on a Fritz!Repeater 3000 using the following instructions:

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=148d29d47b1d555d0058dcc5dda450b74c4628ec

I misconfigured the network and cannot access the box now. So I am trying to reinstall 21.02 using the same steps, but step 5 (Box access the TFTP server) doesn't work. It switches to 192.168.1.1 and is not reachable with this IP after a couple of seconds:

From 192.168.1.70 icmp_seq=11 Destination Host Unreachable
From 192.168.1.70 icmp_seq=12 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2050 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1027 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=3.08 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.19 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.16 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=0.728 ms
From 192.168.1.70 icmp_seq=66 Destination Host Unreachable
From 192.168.1.70 icmp_seq=67 Destination Host Unreachable

I tried the atftpd and the dnsmasq as TFTP server...but the box doesn't access the TFTP server.
Any idea?

Thanks

[frollic]

you can't assume TFTP/uboot will answer pings, it contains only very basic network functionality,
using it as proof of status is ..... well, uncertain or risky.

[GqSteve]

I agree, but I don't see in the logs the 192.168.1.1 accessing the TFTP server....even if I wait 5mins.

Upon the description for installing 21.02, I thought that "while the box was answering pings"...it was actually accessing the TFTP server and then it should take a couple of minutes to boot.

[frollic]

regarding the TFTP server, make sure there's no firewall blocking the calls.

[GqSteve]

Firewall is deactivated.

[GqSteve]

I setup a second machine with the IP 192.168.1.70 and with an atftp server (atftpd --daemon --no-fork --logfile - /srv/tftp) running that hosts the FRITZ3000.bin file. Also in this case...I didn't see the Fritz!Repeater accessing this TFTPserver after loading the U-Boot to it (with ./eva_ramboot.py --offset 0x85000000 192.168.178.1 uboot-fritz3000.bin).

Should I report it as a bug?

[frollic]

You could, but I'm pretty sure the scripts and the uboot didn't come from openwrt, so you'd have to do it someplace else.

[GqSteve]

I found finally a way to reinstall it. These are the steps, if someone faces the same problem.

With a Windows PC download the recovery tool from AVM FTP server for this box and recover it.

The following steps are related to the instructions:

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=148d29d47b1d555d0058dcc5dda450b74c4628ec

I highlighted the differences:

1. Grab the uboot for the Device from the 'u-boot-fritz3000'
   subdirectory. Place it in the same directory as the 'eva_ramboot.py'
   script. It is located in the 'scripts/flashing' subdirectory of the
   OpenWRT tree.

2. Assign yourself the IP address 169.254.143.10 (Netmask 255.255.0.0). Connect your
   Computer to LAN port 1.

3. Connect Power to the Box. As soon as the LAN port of your computer
   shows link, load the U-Boot to the box using following command.

   ./eva_ramboot.py --offset 0x85000000 169.254.143.1 uboot-fritz3000.bin

4. The U-Boot will now start. Now assign yourself the IP address
   192.168.1.70/24. Copy the OpenWRT initramfs (!) image to a TFTP
   server root directory and rename it to 'FRITZ3000.bin'.

5. The Box will now boot OpenWRT from RAM. This can take up to two
   minutes.

6. Copy the U-Boot and the OpenWRT sysupgrade (!) image to the Box using
   scp. SSH into the Box and first write the Bootloader to both previous
   kernel partitions.

   mtd write /path/to/uboot-fritz3000.bin uboot0
   mtd write /path/to/uboot-fritz3000.bin uboot1

7. Remove the AVM filesystem partitions to make room for our kernel +
   rootfs + overlayfs.

   ubirmvol /dev/ubi0 --name=avm_filesys_0
   ubirmvol /dev/ubi0 --name=avm_filesys_1

8. Flash OpenWRT peristently using sysupgrade.

   sysupgrade -n /path/to/openwrt-sysupgrade.bin

Hope it helps.