You can download the recover.exe from AVM which will blast any version of the OS onto the router. You can use wayback machine to get an old one.

This is the URL for the current recovery program, put that into wayback machine and get an old one from before it all went t!ts up. Then turn off auto updates.
https://download.avm.de/fritzbox/fritzbox-7530/other...

e.g.
https://web.archive.org/web/20230531133413/https://d...

or for AX
https://web.archive.org/web/20230912221415/https://d...

EDIT: wayback machine links don't seem to work for very long, so just put the 1st url into waybackmachine yourself and find a pre-8.0 OS.
EDIT2: seems wayback machine is down at the moment (I thought the links had expired)

Edited by Glenn2 (Tue 22-Oct-24 16:09:17)

Turns out they are sending me a 7530, not the AX as they have run out. At the same time I get an email saying there is no problem at their end and asking me to plug into the test socket.

And a phone call telling me it must just be my hardware that's failed.

Done with Zen tbh.

I have been reading this thread with interest. I have an old 7530, and a newer 7530AX - both originally from Zen, though I am not and never have been with Zen for broadband. The 7530 is now just a mesh repeater, and the AX has the VDSL connection.

Both were regularly updated with the recent 7.90 beta versions, and 8.00 since it bacame available from AVM. I have not seen any unexpected disconnections, and the AX has now had the current connection for over 27 days.

This seems to support the theory that it is not the hardware, or the AVM software that is causing the problems, but something that Zen have messed up in their distribution of OS8.

I just got off an infuriating live chat with Zen. They insisted the problem is fixed and nobody else has reported the issue since. Then I was asked to plug the loan router to the test socket. The loan router on v7 works just fine so not sure what this will prove. I am pretty certain they will end in them saying its a hardware (router problem). Then I will have to update the loan router to v8 to prove it's not.

I think I am also done with Zen

Edited by Gattsu80 (Tue 22-Oct-24 17:14:05)

I'm afraid that I can't agree with that deduction. No-one has any issue with the 7530AX on version 8. The 7530 is coasting along being a simple mesh repeater.

The reason fir the problems is that the 7530 has run out of puff. Might be OK for simply a modem or a repeater but to do heavy-lifting ? Foget it.

It is a hardware problem. Simply run out of guts to run the new version.

Their 'explanation' does not stand up. 'The recent firmware update triggered an automatic reboot of the device, which may have appeared as a disconnection to some users. We have identified and stopped this auto reboot '

It might have triggered an automatic reboot when the update was first loaded and run. That is normal behaviour for a lot of updates across the board. But it is a one-off. How on earth can Zen say that they 'stopped this auto-reboot' ? Either their system was constantly sending out ...somehow...an auto-reboot command to the router (if such a command exists' or it's a combination of the new version and the existing hardware in the 7530. Over which Zen has no control.

The former scenario ...that they were sending out a reboot signal..is easily dismissed because there are enough people on here who have disabled all remote control of the router by Zen....and yet the router still keeps rebooting.

Zen are not doing their star rating any good here.

Edited by countryman69 (Tue 22-Oct-24 17:41:42)

I agree. It's clearly working fine on the AX model (which they refused to send me)

I found the Fritz UI had got very slow and flaky, the last time I tried it (about 6 months ago I think).

I had previously abandoned it for OpenWRT a couple of years ago, although that was due to wifi bugs*. Just did a brief test earlier this year to see if the wifi bugs I had were fixed (they weren't) and it was so painfully slow. Went back to OpenWRT again.

*The bug in question was that even when manually forcing a low-numbered 5GHz channel (e.g., 42) it would often leave it for a high-numbered one that most of my equipment cannot even receive, meaning most of my devices had no wifi.

In reply to a post by countryman69:

It is a hardware problem. Simply run out of guts to run the new version.

I doubt it. The CPU load as shown in the UI hovers around 50%,

Besides, there's very little in terms of new functionality. Same VDSL modem, same NAT, same wifi. Changes from v7 to v8 were mostly cosmetic, plus tweaking of a few smart-home functions that hardly anyone uses anyway. Given that v7.59 was able to run under smoothly a very heavy load, a suggestion that the v8 crashes are caused by normal load doesn't appear plausible.

In reply to a post by countryman69:

Their 'explanation' does not stand up. 'The recent firmware update triggered an automatic reboot of the device, which may have appeared as a disconnection to some users. We have identified and stopped this auto reboot '

It might have triggered an automatic reboot when the update was first loaded and run. That is normal behaviour for a lot of updates across the board. But it is a one-off. How on earth can Zen say that they 'stopped this auto-reboot' ? Either their system was constantly sending out ...somehow...an auto-reboot command to the router (if such a command exists' or it's a combination of the new version and the existing hardware in the 7530. Over which Zen has no control.

Agree that their statement is bonkers.

My router is showing TR-069 as "inactive" under Diagnostics / Security (although what should be an "IP services" tab under Account Information, with more granular controls, doesn't exist or is hidden).

In reply to a post by countryman69:

The former scenario ...that they were sending out a reboot signal..is easily dismissed because there are enough people on here who have disabled all remote control of the router by Zen....and yet the router still keeps rebooting.

Zen are not doing their star rating any good here.

Agree.

Edited by NewMoon (Tue 22-Oct-24 20:24:31)

Where do you find CPU load ? I can see energy consumption but not CPU load.

Assuming you are right then what do you think is causing the reboots ?

Edited by countryman69 (Tue 22-Oct-24 22:30:32)