Converting a German targeted Fritz!Box Fon Wlan to an International version

[HnZCaM]

Ja, bis jetzt gab es keine Unterbrechungen mehr... werde das ganze jetzt ein paar tage testen und dann wieder hier reinschreiben...

 

[xagapiou]

FB 7170 dsl speed problem

Hello everybody,
This is my first post and i cant speak german so i would appreciate if someone can explain me in english.
I get to the point, I have taken a 1&1 FB 7170 and converted it to english Annex A
by executing these lines
c:\>telnet 192.168.178.1
#echo "kernel_args annex=A" > /proc/sys/urlader/environment
#echo "annex A" > /proc/sys/urlader/environment
#export ANNEX='A'
#export CONFIG_ANNEX='A'
and then restart the FB.
again i telnet and execute the following command:
#echo "firmware_version avme"> /proc/sys/urlader/environment
After i downloaded this
and run it to make it english.
All worked good. I have internet connection. But with worse speeds. With my FB 5140 (english and Annex A) i can synchronize to 17700-18100Kbps and with 7170 no matter how many times i re-synchronize i get only around 13500Kpbs.
I would appreciate any ideas or help.

P.S. I wrote down the procedure so that i can share it with everyone

-Andrew

 

[el_valiente]

#echo "kernel_args annex=A" > /proc/sys/urlader/environment

The parameter "kernel_args annex=A" forces an AnnexB Box to behave like AnnexA. It works, but with less speed - as you noted.

The following three lines are not necessary, but harmless:

#echo "annex A" > /proc/sys/urlader/environment
#export ANNEX='A'
#export CONFIG_ANNEX='A'

And finally, the command

#echo "firmware_version avme"> /proc/sys/urlader/environment

tells the Box to accept english firmware.


Summary:
It seems, your FB7170 was originally AnnexB. You converted it to AnnexA with english firmware - congratulations. Now, the FB7170 works well with AnnexA, but your FB5140, which is AnnexA from factory, works a little better. That's all.
You should be satisfied.
.

 

[xagapiou]

so u think this is a hardware problem? Perhaps some configuration might make it behave better...dont know just thoughts


Also can anyone upload the driver needed for the fritz 7170 to work as print server. I mean the driver that it should be installed in every
computer which want to print in the virtual local AVM port.
thank you
-Andrew

 

[nono11]

fritzbox 7170 nearly dead - doesn't stop to reboot

hi,

I have a problem concerning my fritzbox.
I bought a fritzbox 7170 annex A with german interface on ebay. It seems that it is the old HW (version 1). After lot of reading on this forum I tried to convert the box in english interface with the file 1/ fritz_as_avme_newer.tar and after the recovery.

After run the update with the first file "newer.tar" the box reboot and I tried to run the recovery. I tried the recovery 4.57 file for 7170 english annex A and annex B and also the german version 4.67 for the 7170 but nothing is working and I cannot access anymore to my FB. It seems that the FB doesn't stop to reboot. I don't received any IP addresse and the connection icon in the task bar has a yellow "pannel".

Do you have an idea or I can put my box to the garbage can? :beerdigu:

thank you for your help.

Nico

 

[el_valiente]

... or I can put my box to the garbage can?

No, your 7170 isn't dead, it is just a little sick. The permanent reboot loop is a well known symptoma. It is easy to cure, using ftp/adam2 access to the bootloader and adjusting the environment parameters.

If you are not familiar with ftp/adam2, you should first try the following:
According to your explanation, the 7170 was selled to you as a original version A/CH AnnexA (german). The appropiate recovery file is fritz.box_fon_wlan_7170.annexa.04.43.recover-image.exe, which you will find at the FTP server at the avm homepage. Try to execute this file. But I'm afraid, it will not help, too.

The reason seems to be that your 7170 isn't originally A/CH AnnexA, but AnnexB patched with "firmware_version annex=A". In this case the environment parameters are contradictory after running "fritz_as_avme_newer.tar" and the Fritz!Box rebootes continously after any recovery.

The only solution is to correct the environment parameters using ftp access to the bootloader with username and password "adam2". See [post=1205536]here[/post] how to do that (points 1 to 5).

Use "quote GETENV <parameter>" to see the values of the following parameters and post them here in the forum. Then I will tell you the right values.
- parameter annex (value can be "B" or "A")
- parameter HWRevision (value can be "94" or "127")
- parameter firmware_version (value can be "avm" or "avme")
- parameter kernel_args (value can be "not set" or "annex=A")

I suppose, the present values are "annex B", "HWRevision 94", "firmware_version avme" and "kernel_args annex=A".
This combination is "forbidden" and the box necessarily enters into a permanent reboot loop - as it is the case.
.

 

[nono11]

Hi,
Thank you for your quick answer.

I changed my message because I was not able to connect to the box via FTP but in meantime it's working. For info I used this procedure from Marsupilami:http://www.ip-phone-forum.de/archive/index.php/t-138490.html

So the parameters from my box are :

- parameter annex (value can be "B" or "A") =====>B
- parameter HWRevision (value can be "94" or "127") =====>94.1.0.0
- parameter firmware_version (value can be "avm" or "avme")=====>AVME
- parameter kernel_args (value can be "not set" or "annex=A")=====>annex=A
Like you said in your mail ;-)

Is it possible to update this box in english with the annex A?


Thank you for your support. I really appreciate.
nico

 

[el_valiente]

Is it possible to update this box in english with the annex A?

Yes, it is possible.

The environment parameters must have the following values:
- annex B
- HWRevision 94
- firmware_version avme
- kernel_args annex=A
As you write, they do already have these values. That's ok.

Your 7170 is an originally annexB box, which means "annex B" and "HWRevision 94". These parameters can be changed only temporarily! After a reset or shut down of the 7170, they will return to their original values.
Do to this reason, firmware specifically dedicated to annexA can't be used, because it permanently needs "annex A" and "HWRevision 127".

In order to force the 7170 to behave like an annexA box, the permanent setting "kernel args annex=A" must be added. This was already done - ok.

In order to prepare the 7170 to accept english firmware, "firmware_version" must be "avme" (this parameter changes permanently). This was already done, too - ok.

Now the 7170 is prepared to execute the appropiate recovery file. You must use the english version for annexB,
namely "FRITZ.Box_Fon_WLAN_7170.AnnexB.en.04.57.recover-image.exe".
It should work without problems.

I wish you good luck! If you are successful, you will obtain a FB7170 with english firmware, which is still annexB, but will behave like annexA.
It is the same configuration as you have had until now, with the only difference that the menue will be in english.
.

 

[nono11]

Hi,

ok finally it s working! :-D
The recovery was not so easy because the PC didn't found the box (5 reboot and 20* searching). I connected the FB to the power just before to lauch the searching and it was good.

Now the box is in english with the version 29.4.57 and annexA. I will check the modem later today.

A last question, if a new english SW version is released, Can I update my box without problem and if yes with which version (always 29)?

Thank you very much.

Nico

 

[el_valiente]

A last question, if a new english SW version is released, Can I update my box without problem and if yes with which version (always 29)?

Congratulations!

That's a good question!

With the present setting you can update with all (future) english FW versions for annexB. Those are all named "29.xx.xx".

Never try do update with a FW version for annexA (named 58.xx.xx), no matter of german or english language.

If you want to go back to german FW, you con update all FW versions for annexB, named (29.xx.xx). But first you must run "fritz_as_avm_newer.tar" (this will set the parameter "firmware_version" to the value "avm")

Don't worry! Your 7170 will remain "AnnexA", even if you update with a AnnexB FW.
.

 

[aster_dox]

FB-FON: reboots when connecting to Internet after conversion to english/annex A

Hi,
firstly let me apologize because I write in english. I cannot express myself very good in german, but you are welcome to answer me back in german.

I have a problem with two boxes, a FB FON and a FB FON WLAN.
I bought them in ebay (German versions, Annex B), and then I converted them to english (Annex A) using the procedure explained in this threads (FTP + quote commands), then I upgraded to the latest english version.

I used the following recovery files for the conversion:
fritz.box_fon.annexa.en.04.24.recover-image.exe
fritz.box_fon_wlan.annexa.en.04.26.recover-image.exe

Then I upgraded the software to the corresponding .49 version, also english annex A. (probably this I should not have done....)

The boxes booted and worked fine as ATA, but if I try to use them as Router (via LAN port or DSL) to connect to internet through them, both systems reboot and stay in a loop (unless I disconnect the LAN port).

Have I done something wrong with the conversion and update to latest english firmware?

I tried to have them back converted to German, but I did not manage (procedure runs OK, but after reboot keeps on rebooting, I can only recover again with the english firwamre)

I´ll appreciate if could give me any hints here.

Regards,
aster_dox.

 

[el_valiente]

I&acute;ll appreciate if could give me any hints here ...

You did good work, no mistakes.
But you had bad luck: The firmware versions 06.04.49 and 08.04.49 both have an ugly bug: They don't work in ATA mode!

I opened a thread specifically dedicated to this theme, see [post=1149633]here[/post]. Read it carefully and you will know more ...

In order to solve the problem, you must downgrade to an older version! And this is not easy, because you must replace the kernel (mtd2), which is dangerous. And to make it even more difficult, these firmware versions do not have telnet daemon, thus you must work with external telnet.

I did it several times successfully. You can do it, too, but be careful ...
.

 

[telefonicus]

If you can read German you might as well go back to the German firmware versions 06.04.33 and 08.04.34. That wouldn't require a return to the old kernel.

 

[el_valiente]

... you might as well go back to the German firmware versions 06.04.33 and 08.04.34.

Hi, telefonicus

AFAIK it is not possible to "downgrade" the english fw version 08.04.49 rsp. 06.04.49 to the german fw version 08.04.34 rsp. 06.04.33

The reason is the new kernel. It allows only temporarely setting of parameters "HWRevision" and "annex". At every reset of the FB these parameters will return to their former values, which produces a incompatibility of environment parameters (reboot loop).

I believe the only solution is the one I suggested: aster_dox must go back to the old kernel ...
(opening a ticket at AVM customer service seems logical because of the bug in an official fw version - but it isn't possible, because the FB isn't the international version)
.

 

[telefonicus]

What new kernel, 2.7? Am I missing something? Please update me.

xx.04.33 (.29 and higher) is kernel 2.6 AFAIK.

 

[el_valiente]

What new kernel, 2.7?

Sorry, I didn't specify well. You didn't miss anything.

I don't know any kernel 2.7. Firmware xx.04.49 has kernel 2.6, as well as xx.04.33/34. That I meant with "new kernel".
The problem is not a different kernel in english an german firmware. But the problem is, that kernel 2.6 allows only temporary parameter setting.
After every reset the former values reappear. That leads to a continuous reboot loop.

aster_dox installed the english firmware xx.04.49 annexA. In order to downgrade to german firmware xx.04.33/34 annexB, he must change the parameters "HWRevision" and "annex". And this isn't possible permanently with kernel 2.6.

That's the reason why he must downgrade to "older" kernel 2.4. With that kernel any permanent parameter change is possible.
.

 

[aster_dox]

Hi guys,
thanks very much for your help.
I confirm el_valiente is 100% right, it is not possible to move back to the latest german versions, though you can run the recovery tool (works), after reboot HWRevision and Annex go back to previous value, making the system to enter a reboot loop.

Could you please point me to the procedure for downgrading to older kernel?
Regards,
aster_dox.

 

[imagomundi]

I used the following recovery files for the conversion:
fritz.box_fon.annexa.en.04.24.recover-image.exe
fritz.box_fon_wlan.annexa.en.04.26.recover-image.exe

All your mess started here! You may never upload an annex-a-image or -even worse- recover firmware to an ORIGINALLY B Box!

Then I upgraded the software to the corresponding .49 version, also english annex A. (probably this I should not have done....)

I agree with you - THIS you should not have done!

Have I done something wrong with the conversion and update to latest english firmware?

Yes - everything!

I apologize for my clear comments. What can you do? BEST and most promissing is "el_valientes" suggestion - but hard to do! Before taking the stony way of downgrading to Kernel 2.4 try to get some information from the box through its ftp server - just as nono11 did - add additionally "quote GETENV firmware_info" and "quote GETENV kernel_args annex".
This procedure serves just to get reliable information on the actual values of your boxes.

 

[el_valiente]

All your mess started here! You may never upload an annex-a-image or -even worse- recover firmware to an ORIGINALLY B Box!

Hi, imagomundi!
You are right - in case of kernel 2.6.
But with kernel 2.4 you can do it. This is the case for e.g. firmware 06.04.24 or 08.04.26. In these firmware one can permanently change the environment parameters, converting an originally AnnexB FB in a real AnnexA FB.
This is what aster_dox did. At that time he had two AnnexA boxes working perfectly.
His mistake was to upgrade to the newest AnnexA version xx.04.49! These FW have the known bug, and they don't have telnet incorporated. That's make life difficult.
.

 

[telefonicus]

fritz.box_fon.annexa.en.04.24.recover-image.exe
fritz.box_fon_wlan.annexa.en.04.26.recover-image.exe

I can't see what's wrong with that. I myself did it a couple of tiimes in order to convert German to English: back to 08.03.37, then switch to English and Annex A (which was possible until that version), then upgrade to 08.04.26. It must have worked, otherwise the upgrade to .49 wouldn't have been possible via the user interface.

If the box is looping there is no other way than trying to recover to the last correct version (.49). You'll first need a working system if you want to downgrade. Try to recover version .49 and let us know what happens.

Good luck!
Telonius