@imagomundi
I've already tried this - well, that's the way it's supposed to be done, as all the guides I found say. If you see my first message, I mention that I even tried to change to avme while the web interface existed (before the reboot loop) so as to "force" its loading, since everytime I run it, whatever I do, it says "it cannot determine the version"... :-(
@el_valiente
When you say "I must continue the update"... You mean exactly what? I mean, the move I must do... Re-select the file and hit update, or hit the buttom at the bottom (that means reboot, but I don't remember the German word - sorry)? I've tried both... Nada... :-(
@imagomundi and @el_valiente
Now, here comes the reason I told you about "my experience": I can extrapolate from the events and find some meaning about what happens. Let me explain...
The message I mention (about the version) MUST be a check in the firmware-restore file, to "see if the device is compatible/if it is appropriate to go on with the update". That's where the procedure gets stuck. Normally, it would detect the router, say something like "fritzbox found, version yadda-yadda-yadda, starting update"... But it doesn't! It does find the box, but it seems like it checks the version and thinks the model/the router isn't appropriate to commence the update. That's (I guess) the reason it throws me a message that "it cannot determine the version". Like, say, trying to update a camouflaged Zyxel router with a fritzbox firmware. Yeah, I know, science-fiction, but that's the situation:
* Router is set to language-standard required by the update (avme)
* Router is the right one for the firmware-recovery (and vice-versa)
* The procedure starts and the firmware-recovery searches "to find the version of the router"
* It finds the router
* It checks (I suppose) the router
* It mentions that "it cannot even read its version"
That's as I can put it in plain English - and by the way, sorry for any mistakes or misuse of the language, as I happen to be Greek...
Sooo... Any ideas? Could there be some way that the firmware got "locked", that it "cannot be read"? That's why I mentioned earlier the example with the file/folder usage rights. Think of the firmware-recovery as a user and the data on the router as... well... a folder. If the user doesn't have access to the data, he cannot read it or modify it. That seems a similar situation to my problem: the firmware-recovery can "see" that "there is a router", but "it cannot see which one it is to update it"...
Best regards
Ducklord
PS: I tried changing cables. Used the yellow one that came with the fritzbox. Nothing... Same problem... :-(