
and the kernel booted! Of course, it swore at the file system and the breakdown of mtd blocks and hung, respectively, as expected. His CFE can change the ID board to some prefedined list, it seems to put something out there with digits and buoys SV, and since we have Linux open source -) (and I was too lazy to assemble the toolchain and then honestly rebuild the kernel) patched the linux kernel binar from OpenWRT (after reading in the source what they generally are and which line is more convenient to patch -)) Which, of course, is not supported, it knows such a percent (BCM6338), but at first it swore at the Unknown Board. from it I did what I wanted to do with the F660: I took the kernel from OpenWRT and loaded it on the ZTE831. You won’t believe - now I have exactly this device on the table and I’m smoking this article exactly (while I’m reading about what JTAG is in the context of my bricked F660). Here is an article about adsl 831 - there a person just wrote a compiler-decompiler. IMHO, you need to find a way to unpack - package the firmware.
