Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden. Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Can you see the point now? I had seen this result in another case before. This was the reason for my suggestion. Unfortunately I do not dispose of fw 04.26.
Normally should not be necessary but in these cases with very old firmwares one never knows. If you try to switch back to B I recommend to use "haveaniceday''s" file from [THREAD=68979]this[/THREAD] thread
You might give it one more try and make a complete recover with RECOVER-EXE 04.15 which you can still download from AVM*s ftp server.
Once your box runs with 04.15 it should be no more a problem to upload 04.33.
I am just trying to remember... the old pseudoimages issue a "echo "annex B" > /proc/avalanche/env" command, but I'm afraid the bootloader won't care much about it since there is no Linux filesystem at boot time yet. Or is /proc/avalanche/env just the Linux way to the bootloader's "quote SETENV" variables?
EDIT: two coffees later my memory is back Yes, that's exactly how the old pseudoimages work, setting up the bootloader environment to allow the appropriate recovery image. So you should be able to recover to 14.04.15 and then upgrade.
Guys, thanks for your help, I successfully updated to .33 after many unsuccessful tries.
Last night, or should I say early this morning, I tried to switch back to Annex B.I used telefonicus fritz_as_annex_b_kernel_args_newer script, got an error message but after modem restart it was annex B. I guess error happened because I used haveanicedays script for switching to annex A. Then, I tried several german firmwares, .15,.26 and .33 but without success.After that, I tried to switch back to annex A, but haveaniceday script didn't work for me, so I updated with telefonicus script.
And today, I tried again to switch back to annex B with haveaniceday script. Everything seems to be ok, but when modem restarted it still was annex A. Then I tried .26 firmware and finally it was ok. After that, I easily updated with .33.
Now, is there is way to change interface to english?
:groesste:
Achtung!
Die angegebene Datei enthält keine von AVM für dieses Gerät freigegebene Firmware.
Wenn Sie nicht freigegebene Firmware in der FRITZ!Box installieren, kann dies zum kompletten Funktionsverlust der FRITZ!Box führen. Weiterhin verlieren Sie alle Ansprüche auf Support, Garantie und Gewährleistung für Ihre FRITZ!Box.
Verwenden Sie ausschließlich Firmware, die von AVM für dieses Gerät freigegeben ist. Nur dafür kann AVM die volle Unterstützung der Funktionalität Ihrer FRITZ!Box sicherstellen.
Freigegebene Firmware-Dateien für Ihre FRITZ!Box sind:
- von AVM erstellt und herausgegeben
- für Ihr FRITZ!Box-Modell erstellt
- mindestens so aktuell, wie die auf der FRITZ!Box installierte Firmware
Does it show the option "Update fortsetzten“ ("Go ahead with the update")? Under normal conditions I would say "Don't be scared, just click it". However, I don't know the complete flashing history of your box. Let's make sure the bootloader environment is ok. Please make a copy of the support data (click on the "Support-Daten erstellen" button) and post the first 16 lines like this:
Support Data
------------
Sat Jan 1 01:03:52 CET 2000
2.6.13.1-ar7
HWRevision 76
ProductID Fritz_Box_FON_2_WLAN
SerialNumber 0000000000000000
annex B
autoload yes
bootloaderVersion 1.203
bootserport tty0
bluetooth 00:04:0E:FF:FF:07
cpufrequency 150000000
firstfreeaddress 0x946B1D78
firmware_version 1und1
firmware_info 14.04.33
Does it show the option "Update fortsetzten“ ("Go ahead with the update")? Under normal conditions I would say "Don't be scared, just click it". However, I don't know the complete flashing history of your box. Let's make sure the bootloader environment is ok. Please make a copy of the support data (click on the "Support-Daten erstellen" button) and post the first 16 lines like this:
Is "kernel_args annex=A" really listed at this position? If yes, it's been written into the bootloader environment. How did you manage to get it there?
Is "kernel_args annex=A" really listed at this position? If yes, it's been written into the bootloader environment. How did you manage to get it there?
Yes, sure, that's what the pseudoimage does: echo "kernel_args annex=A" > /proc/sys/urlader/environment. I was just puzzled because there's no such entry in my annex-B box.
Yes, sure, that's what the pseudoimage does: echo "kernel_args annex=A" > /proc/sys/urlader/environment. I was just puzzled because there's no such entry in my annex-B box.
Achtung!
Die angegebene Datei enthält keine von AVM für dieses Gerät freigegebene Firmware.
Wenn Sie nicht freigegebene Firmware in der FRITZ!Box installieren, kann dies zum kompletten Funktionsverlust der FRITZ!Box führen. Weiterhin verlieren Sie alle Ansprüche auf Support, Garantie und Gewährleistung für Ihre FRITZ!Box.
Verwenden Sie ausschließlich Firmware, die von AVM für dieses Gerät freigegeben ist. Nur dafür kann AVM die volle Unterstützung der Funktionalität Ihrer FRITZ!Box sicherstellen.
Freigegebene Firmware-Dateien für Ihre FRITZ!Box sind:
- von AVM erstellt und herausgegeben
- für Ihr FRITZ!Box-Modell erstellt
- mindestens so aktuell, wie die auf der FRITZ!Box installierte Firmware
I get error message that I copy/pasted in my previuos post.
What will happen if I use recovery image? Is fritzbox gonna go back to .31 firmware? Is this operation safe? Is it gonna be annex B again?
@garson: Just to assist "telefonicus" a little: I DO NOT BELIEVE THAT YOU GET THE SAME MESSAGE AGAIN AFTER CLICKING "UPDATE FORTSETZEN". First you said that after the message deployed in your #1034 you get at the end the message "Update fortsetzen". If you really click that I'm pretty sure you won't get the same message again! If you were not corageous enough to do so - please tell "telefonicus"