fritz box 7170 dead

Hi and Welcome!

Do you have a manual for the 7170, english Version...
There you can read, that you need the default IP-Adress 192.168.178.1/255.255.255.0 or 169.254.1.1/255.255.0.0 for the Box and for your PC an IP in that area.

That small button got to be the WLAN on/off Switch.

To reset, just disconnect the power cord and reconnect a couple seconds later...

Bye, Jojo

The red cable is just a normal LAN cable, nothing special.

The red cable's advantage is that it's short. Sometimes the recovery software won't find the Fritzbox through a long cable.

From what you wrote I supposed you've got the international model (that's why I suggested to resell it as it is more expensive than the German model).

If only the info LED is blinking and you can't get access to your Fritzbox it has probably suffered a software (or configuration) accident which may require a recovery. To sort out your situation and to determine which recovery software is appropriate please answer a few questions:

Is it an international model at all? Or did you buy a converted German model (on Ebay)? What is the Artikel-Nr. or Part-No. on the label (starts with 2000)?

Did you get it in this state? Did you or someone else try to change the language and/or Annex settings? Do you have any idea about the actual firmware version? 58.04.xx or 29.0x.xx?

Please let us know and we'll be glad to help you.

best regards,
Telonius

try to recover using the appropriate recover.exe. Not sure what this got to be an international Annex A or international Annex B version, guess you'd have to try both

Part-No.: 2000 2387 is an international model, otherwise it would read Artikel-Nr.: 2000 nnnn. You'll need the FRITZ.Box_Fon_WLAN_7170.AnnexA.en.04.57.recover-image.exe

After successfull recovery update with fritz_as_annex_b_kernel_args_newer.tar.

Ignore warnings / error messages and click on continue / restart.

Good luck!
Telonius

I assume you have a Windows-XP PC. If not, ask a friend.

Connect your PC to the Fritzbox via the Ethernet (LAN cable) and set the IP address of your PC's LAN adapter to 192.168.178.XXX (XXX between 003 and 253), the subnet mask to 255.255.255.0 and the gateway interface to 192.168.178.1 (if it doesn't work after several trials try 192.168.178.2)
IMPORTANT:
*Set your LAN adapter to 10 Mbit/s Half Duplex EDIT: (only if automatic rate negotiation doesn't work).
*Make sure your LAN adapter has a fixed IP address, e.g. 192.168.178.10
*Disable any IP-filtering or firewall
*Diasble any other LAN adapters
*Make sure you are accessing the LAN directly (not through an application software)
*Use a short LAN cable! AVM recommends to use the red LAN cable for firmware updates/recoveries.

Start the recovery program first hand and follow the instructions (this first time only). It will probably fail again but it will establish a steady connection to the bootloader. do not disconnect the power supply after the recovery attempt!

If a warning pops up like 'Mediasensing is enabled on your PC' please stop the recovery program (answer 'NO' to the prompt) and look here

Open a "COMMAND" console window (aka "DOS window") and enter the following instruction:

Now enter the following commands (you can copy and paste all the lines at once. Use the right-hand mouse button to paste. Enter the whole batch of commands in one step, including the login sequence and the bye command):

ftp 192.168.178.1
adam2
adam2
quote GETENV HWRevision
quote GETENV ProductID
quote GETENV annex
quote GETENV firmware_version
quote GETENV firmware_info
quote GETENV bootloaderVersion
quote GETENV urlader-version
quote GETENV prompt
bye

If the Fritzbox does not react to the ftp command enter CTRL-C to cancel it and try again.

Then post your results.

strange...

Something or someone must have wiped your environment variables. It should have looked like this:

ftp> quote GETENV HWRevision
HWRevision 127.1.1.0

200 GETENV command successful
ftp> quote GETENV ProductID
ProductID Fritz_Box_7170_AnnexA

200 GETENV command successful
ftp> quote GETENV annex
annex A

200 GETENV command successful
ftp> quote GETENV firmware_version
firmware_version avme

200 GETENV command successful
ftp> quote GETENV firmware_info
firmware_info 58.04.57

200 GETENV command successful
ftp> quote GETENV bootloaderVersion
bootloaderVersion 1.309

200 GETENV command successful
ftp> quote GETENV urlader-version
urlader-version 1309

Zum Vergrößern anklicken....

Fortunately the bootloader is still working. You can set the variables yourself:

ftp 192.168.178.1
adam2
adam2
quote SETENV firmware_version avme
quote SETENV annex A
quote SETENV urlader-version 0000
quote SETENV bootloaderVersion 0.000
quote SETENV firmware_info 58.04.30
quote GETENV HWRevision
quote GETENV ProductID
quote GETENV firmware_version
quote GETENV annex
quote GETENV urlader-version
quote GETENV bootloaderVersion
quote GETENV firmware_info
bye

Then start the recovery again. It can take 5 minutes or more. Once the Fritzbox is successfully recovered it will start up and you can set the modem standard to Annex B with the pseudo image fritz_as_annex_b_kernel_args_newer.tar (see above).

Good luck!

ps
If your bootloader doesn't accept the quote SETENV commands there's a chance you've got a firmware revision below 58.04.29. Then replace the spaces between variable name and value by a comma, e. g. quote SETENV annex,A

sabcat schrieb:

... What else could i do?

Zum Vergrößern anklicken....

Hi, sabcat!

With Telefonicus you do have a very good coach, so you don't need my help.
But your problem seems quite astonishing to me, thus I will comment it shortly, until Telefonicus will be back.

You did use the "quote GETENV" commands correctly and the system answered "successful"

ftp> quote SETENV firmware_version avme
200 SETENV command successful

Zum Vergrößern anklicken....

But when you asked to confirm with "quote GETENV", the system says "environment variable not set"

ftp> quote GETENV firmware_version
501 environment variable not set

Zum Vergrößern anklicken....

This strange behavior happens with the parameters "firmware_version", "annex" and "firmware_info". The 7170 doesn't accept your input!
Other parameters were accepted correctly, e.g. "ProductID", "urlader-version" and "bootloaderVersion". Why these and no others ???

I modified many FritzBoxes in the past, but I never had this problem! I don't know the reason!
The only suggestion I can give you is to type in the "quote SETENV" commands step by step. I mean as follows:

ftp> quote SETENV firmware_version avme
the answer should be "200 SETENV command successful"
ftp> quote GETENV firmware_version
the answer should be "firmware_version avme"

and so on with the other parameters ...

If it doesn't work, I have no other idea. In that case I must suppose that your 7170 suffers from a hardware problem ...
.

sabcat schrieb:

... Beh, does it mean that my fritz box is definitely dead?

Zum Vergrößern anklicken....

Could be, I don't know. Let see how Telefonicus thinks about it ...

By the way: You better delete the full quote of my post. The Mods in this forum hate full quotes ...
.

Very strange indeed. What does the recovery program say?

Try again:
ftp 192.168.178.1
adam2
adam2
quote SETENV annex A
quote SETENV firmware_info 58.04.30
quote SETENV firmware_version avme
quote GETENV HWRevision
quote GETENV ProductID
quote GETENV firmware_version
quote GETENV annex
quote GETENV urlader-version
quote GETENV bootloaderVersion
quote GETENV firmware_info
bye

If all doesn't work: install ncftp and copy your flash memory contents on hard disk.

Prepare the LAN connection like before (or simply don't disconnect the power) and enter the following ncftp commands:

open <a dialog box will pop up; click on EDIT and enter 192.168.178.1, adam2, adam2 etc.>
debug
binary
quote MEDIA FLSH
quote PASV
get -z mtd2 bootloader.bin
get -z mtd3 mtd3.bin
get -z mtd4 mtd4.bin
bye

After each get command something like this should appear:

mtd2.bin: 64.00 kB 98.31 kB/s

If the copy process takes longer than, say 30 seconds you can safely abort it with CTRL-C. Try to continue with the next get command. If that doesn't work you must start a new session (open). Use the command history function (arrow up).

Then zip the binary files and and append them to your post for inspection.

Good luck!
Telonius

ps
Disclaimer: I'm writing this without the possibility to test it myself right now. Can someone check my ncftp commands please?