I was googling squashfs4 AVM, I stumbled upon this thread https://www.ip-phone-forum.de/threads/please-tell-me-how-to-unpack-filesystem_core-squashfs-squashfs-4.299015/
PeterPawn said: "You could use the version from my GitHub repository (https://github.com/PeterPawn/YourFritz/blob/binaries/bin/x86/unsquashfs4-avm-be) or you have to build your own."
However, that link isn't valid anymore, I don't know if he just removed it or Github changed its structure.
thanks for the info.
i recall that error, delete the repo, clone and chmod -R 775 git_folder should fix it.. pretty sure i didn't mess around with umask (i'm not on my main pc now need to check).
i have freetz git repo cloned in march, and i'm sure i have the unsquashfs4-avm-be bin ready to use built on fedora 31(or 32?) on main pc, but i don't know if there are any license issue and if i can post the bin here.
i can try later on my main pc to clone again freetz git repo and let you know if the tool is actually there.
Note that I don't use these precompiled tools, but build them from the freetz repository myself.
Update: direct links
@Corphish FWIW i have no problem at all building fresh cloned freetz repo, unsquashfs4-avm-be is in the tools folder.
git clone https://github.com/Freetz/freetz
cd freetz/
make tools
cd tools/
./unsquashfs4-avm-be
SYNTAX: ./unsquashfs4-avm-be [options] filesystem [directories or files to extract]
...
...
...
for umask error try chmod -R * 775 or 777 freetz folder and try to build, if it gives error again try umask 0022 command inside freetz folder.
Thanks, I really appreciate your help! luckily, @moeller0 has sent me the extracted bin, I flashed it and everything seems to be fine except that the DSL led sometimes goes off while the internet connection is being intact, I've once encountered this bug with the original firmware coming with OpenWrt but never with DM200 firmware. not a big problem though, it rarely happens.
FWIW i have no problem at all building fresh cloned freetz repo,
unsquashfs4-avm-beis in the tools folder.
Umm, that's strange but maybe it's possible that something that doesn't appear in the repo to announce itself after building? as I really can't find it in the tools folder, I'm just trying to learn.
for umask error try
chmod -R * 775 or 777freetz folder and try to build, if it gives error again tryumask 0022command inside freetz folder.
Thanks, that's good to know, gonna try to extract the bin again myself so I can do it in the future. by the way, I assume that everything worked good for you, were you able to extract and flash it successfully?
And If you don't mind I just have a couple of questions...
a) Should I care about the annex thing if I'm using VDSL? my previous ADSL modem was syncing on annex A, but now OpenWrt report in the overview section that I'm on VDSL annex B.
b) What is DSL tone? How to determine it, should I grab that info from my ISP?
there's a make file for that.
extract yes:
vr9-B-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 9.1.4 | ADSL Annex B for VRX200, version: 9.0.D
sha1sum vr9-B-dsl.bin
ab8aeaf0894643356fa66a87304f388f43ee31e3 vr9-B-dsl.bin
flash/test no. in my limited testing with other dsl firmware i haven't found any big difference in stability/performance for my link. i'm using firmware that is in official openwrt image and is super stable - no issue at all.. "covid-19 lockdown" tested 
the only big difference with stock openwrt firmware is the vectoring support, which my link don't use.
AFAIK vdsl is annex b
info usually provided by isp, i don't even know exactly how all those values work.. @moeller0 might know a lot more on this..
In VDSL the actual frequency distribution band plans are listed in Annex A for North Amerika, Annex B for Europe, and Annex C for Japan, not sure where the resr of the world falls into.
ADSL before was different, e.g. Annex B descrbes a bandplan compatible with german ISDN... If your internet works with the current Annex, I would not worry too much.
In essence you need to pick a tone set supported by the DSLAM see https://www.google.com/url?q=https://www.itu.int/rec/dologin_pub.asp%3Flang%3De%26id%3DT-REC-G.994.1-201004-S!Amd5!PDF-E%26type%3Ditems&sa=U&ved=2ahUKEwi4vMqunIbsAhWPCewKHQqPDcIQFjABegQIABAB&usg=AOvVaw1H7D3oRhnT-vnl397EN38G for some details about mandatory tone sets per Annex.
Hey! I have flashed the fritzbox firmware and everything seems to be fine, but after uploading the bin, my free space got reduced by almost 1mb, that's obvious I know, but I just want to know if I can free up some space by getting rid of the old DSL firmware, if so what files should I remove in that directory?
I also was wondering if I can remove dsl annex A firmware since I'm using annex B, or annex B patch does depend on it?
As with every file/package that comes with the pre-built squashfs image: No, you can't remove it, the contents of the squashfs file system are not modifiable. You can only mark something as deleted, but that doesn't free up any space.
Interesting, I think it's time to learn how to build a custom image, this should help me implement in the desired DSL firmware, right?
But for now, the only way to retrain that 1mb is to revert back to the original firmware, then remove fritz!box bin?
You can absolutely, and very easily, include your own files in a custom image, you don't even need to do a full custom build for that, the "abbreviated" image builder will do that just fine. But I actually never tried removing single files, according to the documentation it should be possible but it's a bit of a hassle since it's not something the image builder does out of the box.
I don't quite understand what you mean. If you manually, after installing, added a file to the system you can just remove it again. Just like you cannot remove files from the squashfs file system, you also cannot add files to it. Files you install afterwards are not kept in squashfs, but in the overlayfs file system (that, as the name implies, sits "on top" of the squashfs file system and keeps the modifications.)
Thanks for the links, I'll dive into that to see what I can do. I'm also keeping an eye on extroot, it should be a good alternative path to go with. I don't want to bloat the thread with off-topic stuff, I'll do some research on that.
I don't quite understand what you mean. If you manually, after installing, added a file to the system you can just remove it again.
Yeah, that's pretty much what I meant, I uploaded the extracted DSL firmware to /lib/firmware. I have just deleted it after reverting back to the original one, and I managed to regain the wasted 1MB.
for testing purpose you can copy to /tmp aka ram, beware all will be lost with reboot.. otherwise as takimata suggested image builder is the best way to go.. i always prepare my image with files packages directive with all my configs so when i mess around for testing an hard reset will reset to my fully working cofiguration.
for testing purpose you can copy to /tmp aka ram, beware all will be lost with reboot.
That's really a good tip, I configured extroot with a 4GB flash drive so for now, tight storage is no longer an issue
I always prepare my image with files packages directive with all my configs so when I mess around for testing a hard reset will reset to my fully working configuration.
As a newbie OpenWRT user, I tend to bloat my device with a bunch of unnecessarily packages just like a child scrabble about his new world, your approach will come in handy, I'm looking forward to implement it.
Thank you, guys.
If you want the vectoring support firmwares but all this building/extracting nonsense is getting you down. As of 17th Feb 2021, these are the latest firmwares that support vectoring (v9.0).
I hope this is okay to be posting this. If not then my apologies.
Can somebody please send me Annex A and Annex B bin files? There are too many problems to get those bin files extracted from .squashfs file.
Edit: Never mind, I've used 5.9.0.C AVM firmware from https://xdarklight.github.io/lantiq-xdsl-firmware-info/.
Hello everyone and happy 2022. Been trying for a while to extract the contents of the latest FRITZ.Box_7430-07.29.image but to no avail. Used p7zip to get "filesystem.image", binwalk --extract to get 0.squashfs, builded freetz-ng tools (since is the latest supported and unabandoned repository) and got unsquashfs4-avm-be but running it only outputs 1 folder which is "squashfs-root" and nothing more. Tried different unsquashfs4-avm-be binary from github but is the same. Tried building the old freetz repo but it fails at some coding errors. I've been told about an Ubuntu-basted Fritz-OS prebuilt VM but I don't see its tools inside. Any help in unpacking the latest image will be helpful.
I found the fix myself. It was under my nose all along. According to the https://xdarklight.github.io/lantiq-xdsl-firmware-info/ page, the right order of commands is:
7z e FRITZ.Box_7430-07.21.image -r filesystem.image
unsquashfs4-avm-be filesystem.image -e filesystem_core.squashfs
cd squashfs-root
unsquashfs4-avm-be filesystem_core.squashfs -e lib/modules/dsp_vr9/
cd squashfs-root/lib/modules/dsp_vr9/
bspatch vr9-B-dsl.bin vr9-A-dsl.bin vr9-A-dsl.bin.bsdiff
Extracted from FRITZ.Box_7490-07.29.image (vdsl vectoring capable firmware files)
vr9-A-dsl.bin https://fastupload.io/9bc5dPXLmgBzqW2
vr9-B-dsl.bin https://fastupload.io/s6QpaNxxn0BCugT
Hello! The links don't work anymore. Can you post these files again? I'll be very thankful!