-
|
Hello, I have a bricked 4040 that I try to unbrick. The box starts up with all LEDs, then a few times only the power LED and finally ends with the Info LED continuously blinking. If I take a look at the boot output it looks like so:
Yes, this is two times (almost) the same. Try to boot from the second partition after the first attempt failed? And the error message
also sounds logical to me. This is as the box got bricked when a failed attempt to put it in a mesh was made. I tried to unbrick it with
I tried to start it with a stock FW and in fact I could download it to the box:
However the box booted from the uploaded image(?) and ran into the same problem,
and a red info LED blinking. If I'm right the configuration is being rebuild to defaults if it is deleted, and this to my understanding should already suffice to unbrick the box. However I don't know how and where to do it. So the question to recover is how to delete the configuration? BR Peter |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Why do you think, that there another partition exists? AFAIK this model has a SPI flash chip with 32 MB capacity ... there's simply not enough space for a second system.
Definitely not - if it should be possible to start the device from an image loaded to RAM (I don't know it and haven't read reports from others who tried this yet), it would in no case be the "original image" file from AVM. This is only a TAR archive, containing further files needed to install a new firmware version from a running(!) FRITZ!OS system: peh@vidar:~> wget -q -O /tmp/original.image https://download.avm.de/fritzbox/fritzbox-4040/other/fritz.os/FRITZ.Box_4040-08.03.image
peh@vidar:~> tar -tvf /tmp/original.image
drwxr-xr-x 0/0 0 2025-10-13 18:18 ./var/
-rw-r--r-- 0/0 400 2025-10-13 18:18 ./var/content
-rw-r--r-- 0/0 2807 2025-10-13 18:18 ./var/info.txt
-rwxr-xr-x 0/0 11812 2025-10-13 18:18 ./var/install
-rwxrwxrwx 0/0 678624 2025-10-13 18:18 ./var/sblupdate
drwxr-xr-x 0/0 0 2025-10-13 18:18 ./var/tmp/
-rw-r--r-- 0/0 0 2025-10-13 18:18 ./var/tmp/filesystem.image
-rw-r--r-- 0/0 29795592 2025-10-13 18:18 ./var/tmp/kernel.image
-rwxrwxrwx 0/0 633348 2025-10-13 18:18 ./var/tzupdate
-rw-r--r-- 0/0 35 2025-10-13 18:18 ./var/version
-rw-r--r-- 0/0 128 2025-10-13 18:18 ./var/signature
peh@vidar:~>If a 4040 will ever completely start while being booted from RAM, the But why don't you use the original recovery application from AVM? https://download.avm.de/fritzbox/fritzbox-4040/other/recover/ It seems, the primary and secondary boot loader images are still intact - if the environment is it too (see below how to check this), the best option is this application by AVM (for stock firmware). If the recovery program fails, it will give you a hint at least, what's going wrong. And if this doesn't further help you personally, we can restart thinking together about the problem with much more knowledge. Alternatively you could try to read the bootloader's environment yourself (by FTP, e.g. using YourFritz/eva_tools/EVA-FTP-Client.ps1 Line 658 in 2867c9a If there's no environment available (even if I have no clues at all, why any action from the regular firmware would "brick" any FRITZ!Box router by destroying this data), then you can/should create a new one yourself. Look for an example (best a correct one) for a 4040 and replace any (device-specific) data there with the values from your device (you'll find most of them on the sign at the back of the device). After converting the plain text to a TFFS image file, can you upload this new environment to your device - make sure to write it to the correct partitions. Which partition names have to be used? I don't know it for sure. You can find this information either in the But as it's almost ever the case ... you should make sure to use the CORRECT information for the device model and it seems to me, that there are some gaps in your knowledge about the FRITZ!Box eco-system. Don't make it worse - try to find more information (e.g. here: www.ip-phone-forum.de) and if you have additional questions (AFTER searching and reading the already existing information), you can ask there. |
Beta Was this translation helpful? Give feedback.
-
It was just a guess, as I saw the console output twice.
I knew that this is just an archive. The command was just assembled from other questions.
In fact, I did that, long before opening a ticket here. But the recovery tool always stated it can't find the box! With eva_discover I realized the box is not completely dead, it selected an IP-Address and stopped in the FTP-Mode. That's when I opened a ticket. After your answer I tried the AVM-recovery tool again, this time with the current 8.03 firmware (last time I tried with an older version 7.??, as 8.03 wasn't out then). And what should I say? This time the box was found and the tool could reset it into a runnable state. That's why I close this ticket.
Yes, think so, too. These two are the shortest partitions, so it should be any of those two.
|
Beta Was this translation helpful? Give feedback.
Why do you think, that there another partition exists? AFAIK this model has a SPI flash chip with 32 MB capacity ... there's simply not enough space for a second system.
Definitely not - if it should be possible to start the device from an image loaded to RAM (I don't know it and haven't read reports from others who tried this yet), it would in no case be the "original image" file from AVM. This is only a TAR archive, containing further files needed to install a new firmware version from a running(!) FRITZ!OS system: