@seann
Hello, the ./707 ist just a shortcut for the commandline. If the choice of the options are not changed, it starts the script with "./sp-to-fritz.sh -m 707 -n -p -o avm". The entering of an additional IP-address ist unnecessary. If you are using the push-option (the -p in the commandline), an additional IP-address would be automatically added to your network interface. But perhaps there is another mistake:
You've posted:
Yesterday I tried to flash my T-com W701V router with the script. I used the following command:
./sp-to-fritz.sh -o avn -m 701 -p 192.168.1.1
It must be avm, not avn. I believe, that was the reason for the faulty generation of the image. And if you are using the [sudo] ./707, the script starts with -m 707 instead of -m 701. This is just another value, but necessary for the script. I suggest, to run the script again (with the speedport connected) and use the command: sudo ./707 in a terminal window. Then, the script looks for the Telekom and AVM firmware and if they are not found in the Firmware.orig-directory, it tries to load them.
Because your speedport does not work properly at the moment, you have to put the both firmware-packages (fritz.box_fon_wlan_7170.29.04.49.image and fw_Speedport_W701V_v33.04.45.image) manually into the directory Firmware.orig before the script starts, but the rest runs by itself.
Edit: After reading your post again, I discovered another possible mistake. It's in the following sentence:
I skipped the message by pressing enter, after which my machine connects to 192.168.1.1 via FTP to upload the firmware.
Normally, the script don't ask for an uploading via the WebGUI if the option -p is in use, you would be asked to switch the speedport off an on again, then the firmware is loaded automatically. The permanent rebooting of the box after starting normally happens if a complete firmware.image was uploaded by FTP. Because of the faulty commandline (the IP-address in it is too much), I don't know what kind of image was generated. If you upload the firmware manually by FTP, you must only upload the kernel.image, not the complete firmware. If you have a complete firmware-image, the kernel.image must be extracted first.
In a complete image, this file is in the /var/tmp-directory and could be uploaded by FTP manually. And in that case, an additional branding must be set. You've used the TCOM-Firmware before, now the branding must be set to AVM, otherwise you can't reach your WebGUI. The command: SETENV firmware_version avm changes the branding. The script does this if the -p option is used, but because you skipped something I'm not sure that this part runs correctly. Some other environment variables were also set, but the important one is the branding.
greetings, Ernest015
