Replies: 20 comments 5 replies
-
Your device reports to have memsize=128MB ram in bootloader. |
Beta Was this translation helpful? Give feedback.
-
I do not know much about this process. It didn't flash before, either and it also doesn't flash the firmware it ran fine with for months. |
Beta Was this translation helpful? Give feedback.
-
I searched on HW226 inside push_firmware and saw this.
It's probably correct, but I have no idea why that line is commented. |
Beta Was this translation helpful? Give feedback.
-
Just downloaded a new recovery tool for the 7590 (FRITZ.Box_7590-07.59.exe) and ran it.
The box then comes in some kind of boot loop. I then flashed it using the AVM-recovery tool and it came back after flashing. |
Beta Was this translation helpful? Give feedback.
-
I can flash the box using a push_firmware from branch 0e13f57
I can remember it didn't flash immediately then, but never gave it much thought. It's pure the tool "push_firmware" which evolved and rendered it broken for my boxes. Most need the tool only once anyhow. |
Beta Was this translation helpful? Give feedback.
-
Are 91 MB of the 512mb enough to run the image you uploaded? |
Beta Was this translation helpful? Give feedback.
-
This is the box that was stuck in AVM: root@fritz:/var/mod/root# cat /proc/meminfo
I have never really examined the details of the flashing process. |
Beta Was this translation helpful? Give feedback.
-
I could go back a bit less in time and try to find out when the tool becomes unsuccesful on my boxes. It for sure isn't 2 weeks ago, because I noticed this odd behaviour after I setup the new HyperV machine. |
Beta Was this translation helpful? Give feedback.
-
There was no change, check the |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
When I create a new environment with this procedure, I can flash freetz-ng onto fresh "AVM factory resetted 7590" The biggest difference I can see during flashing is that I always have to powercycle twice during flashing for the version of 120 days ago and before. As of the version of 21-04-2024 (or less than 4 days before) I can't use tools/push_firmware to flash freetz-ng on an International 7590. I can now continue to flash new images as long as I use the version of 16-04-2024. The 7530AX were impossible to flash in March. Get a fresh environment:
A lot changed between fd0f6ab and 8bfe266 diff freetz-ng-120days-fd0f6abe24b6a17f0b6eb0905bca7ed62087df13/tools/push_firmware freetz-ng-115days-8bfe2666c504d1abea029a5fb122a6c9800154d7/tools/push_firmware
|
Beta Was this translation helpful? Give feedback.
-
You are mixing some of the 5 different flash methods required for avm devices, 7590 and 7530ax require different one! |
Beta Was this translation helpful? Give feedback.
-
Of course I'm only flashing a 7590 now.
Like I said. I never made any attempt ever to change the bootloader on those FB's I now have a workaround for it and can go to the folder where I have "April 16th 2024-version" and with that I can flash the boxes when they are new. If I can help in any way by running some scripts for you on the box I'm happy to help you solve it. I don't have a 7490 here at the moment, but when I have one here, I can do some tests. After a device is flashed with freetz, they tend to never run run AVM-Fritz!OS again. Thanks for all the input. |
Beta Was this translation helpful? Give feedback.
-
I connected manually with EVA to the box and it seems the "conversation" I'm having with my box isn't as it's supposed to be. The box eventually reports 0x20000000 which is 512 MB:
Here is my correspondence with EVA, most of the time she's not answering:
|
Beta Was this translation helpful? Give feedback.
-
I switched to the lftp client and there it alway gives a consistent result:
|
Beta Was this translation helpful? Give feedback.
-
But why you get 8000000h ? (empty linux_fs_start is normal after avm-recovery) |
Beta Was this translation helpful? Give feedback.
-
7590
It then hangs....
Meanwhile outside that session I do a cat /tmp/evaout it indeed has "memsize 0x08000000" cat /tmp/evaout
7590AX My 7590AX acts similar.
cat /tmp/evaout7590AX
|
Beta Was this translation helpful? Give feedback.
-
For the ram-boot devices the size is limited if some memory is needed for something secial (eg an uploaded image) As push firmware uses (meanwhile) "get env" https://github.com/Freetz-NG/freetz-ng/blob/master/tools/push_firmware#L71 it should be always the full size ... but somehow this does not work for you. So something is nor working as expected. You could edit push_firmware and add somewhere |
Beta Was this translation helpful? Give feedback.
-
Try the
See ( in Dutch): Wissen Fritzbox / root access? |
Beta Was this translation helpful? Give feedback.
-
I confirm that with |
Beta Was this translation helpful? Give feedback.
-
After changing my system I wasn't able to get my Hyper-V machine working again.
I installed a new Debian and Freetz-ng and was able to compile new images again.
These images work on various models.
I've uploaded them using the Freetz webIF.
I was even able to flash the 7530AX which still had the original AVM-software because I was unable to flash them using the old machine with
tools/push_firmware
I also tried to flash a 7590AX and a 7590 and they both came back with the Freetz software they already had.
I then flashed 1 7590 with the AVM recover tool
Now the 7590 is running the standard AVM-firmware
I tried flashing it with tools/push_firmware, but it keeps coming back with AVM-firmware.
Even when I flash a firmware from February this year which I had no problems to flash using tools/push_firmware it keeps coming back with AVM.
There are no disturbing messages during uploading:
Any idea what I can do?
I use International boxes and the firmware is also set to International
So a few months back I could flash the 7490, 7590 and 7590AX, but NOT the 7530AX
Now I can flash the 7530AX, but not the 7490, 7590 and 7590AX
I can flash them using the Freetz interface, though.
The 7590 which I reverted to standard AVM-firmware will stay on AVM until I can get this solved as I'm unable to upload a firmware.
Beta Was this translation helpful? Give feedback.
All reactions