On 2/27/21 6:00 PM, Bjørn Mork wrote:
Hauke Mehrtens <ha...@hauke-m.de> writes:I used the wrong AAHI magic and it was possible to falsh the image over the Web UI, buit the image did not boot, it was unable to find the root fs for me.That's odd. Didn't work in my tests, but I've only tested the GS1900-10HP with the latest stock firmware. But rootfs? Flashing from stock will only work with the initramfs image. The stock web ui will cut the image according to the uimage header, without warning. So everything has to be "inside" the uimage.
Ok, I used the sysupgrade tar, I was surprised that this was accepted at all. ;-)
But there is something wrong with our image code if you are able to flash anything else than the initramfs image from stock. Specifically: The "zyxel-vers" stuff should *not* be appended to the kernel in the sysupgrade image.Where is this check done?AFAICS, only in the stock firmware upgrade "app".I was unable to extract the original firmware with binwalk which would be nice to get some more information about how it is structured.The GPL drop at https://biot.com/gpl/GS1900-10HP(V2.60(AAZI.2)C0).zip is pretty complete. Only a few files are binary blobs. And everything necessary to build an image is included.
Thanks I will have a look at this.
There isn't anything weird with the stock image. It's a standard uimage with a non-standard magic. The list of supported hardware versions is an ascii text file at the end of the real image, but inside the size and checksum coverage of the uimage header.
Hauke
OpenPGP_0x93DD20630910B515.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
