I think from what is shown it takes the same firmware as the one labeled A1
you could test this by uploading a downloaded version that says it's for the A1
Post your text output as actual text please, so it's searchable. Screenshots cannot be indexed by any search engine, you see.
No, you're on a DSA target. The software bridge is there (br-lan). For now there's no LuCI counterpart yet, but you can manipulate it on the command line if needed.
they all require new headers due to your boot loader now requiring them now
I have not done this but you should be able to extract the kernel image from a sysupgrade file
edit it the same & place it back into the archive "sysupgrade file"
well it seems the later DIR-2660-A1's needs this as well
I think as some point they updated the boot loader
it would be better if this mod was added for all the devices
that is the one's built by SGE DIR-878,867,882,1960,2660 & others
it wasn't added due to it not being needed at the time
but it would help in future is someone writes the encrypt part
with would make them web flashable
you could contact them i think it would speed up everything
it would take me a long time to lean how & then another 6 mouths for the commit to got thought
there is a part where \tools\firmware-utils\src\uimage_padhdr.c
add's padding to the standard uboot header
"96 bytes of 00 in this case"
as this area is the part added maybe this is where the
DEVICE_MODEL & DEVICE_VARIANT
from target\linux\ramips\image\mt7621.mk
should be added
I think the only option for the time being is to keep modifying the factory image
I'm going to play in the background
but someone who know what they are doing could do it in a few minutes
I can read the code ok but not so good at writing it
The encryption was already figured out, see dlink-decrypt for details on how to decypt/encrypt stock firmware images. Also worth mentioning the recovery GUI from the bootloader only accepts unencrypted firmware images.
Also, the encrypted image must be signed with D-Link's private AES key in order to be accepted by the web GUI of the stock firmware and each device uses a different key. In other words, unless that private key leaks, no custom firmware will ever be accepted by the stock firmware, even through the SHRS format the router expects is already documented...
it depend on witch boatload your board got form the factory
my original dated Jul-19-2017 will only accept unencrypted ones
I have a later copy of one dated Jul-8-2018 that accepts both
I do be leave it accepts any of the boards encrypted versions of firmware as well 878 & 882
I even tested another clone the DIR-1935 firmware and saved the unencrypted version this way
original dlink firmware for the DIR-878 has the extra 96 bytes as #define PRODUCT_LEN 64 #define VERSION_LEN 16
||uint8_t product[PRODUCT_LEN];|
||uint8_t sw_version[VERSION_LEN];|
||uint8_t hw_version[VERSION_LEN];|
so 1st 64 bytes as device name "DIR-878"
then 16 bytes for software version number "V1.01B04"
then last 16 bytes for hardware version "A1"
so at the moment the blank 96 bytes are add to a default uboot header by
\tools\firmware-utils\src\uimage_padhdr.c