So I saw that the DIR 853 A3 already has it in the approved devices, but I'm not sure if I can work on this DIR 853 A2 device
Do you think possible?
Can't use another devices fw without further investigating, you're risking a brick.
1 Like
Hey,
I'm doing some very detailed research to understand, but I still haven't been able to get it to work.
Get what to work?
Hi @ads119
If you are happy to compile your own image then I am sure you would be able to get it to work easily.
Having said that you should first get a backup of your whole device. If you have access to the console it would be better (to be able to see the logs)/
The A1/A2 is just the A3 with a NOR flash (A3 being NAND).
@Lucky1 is the expert on these devices I am sure he'll be able to provide more guidance.
My advice is to look at the pull request for the A3
And do something similar with the A1. Replace the Nand part with the one from your device (which should be the same with other dlink devices
&nand {
status = "okay";
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
partition@0 {
label = "u-boot";
reg = <0x0 0x80000>;
read-only;
};
partition@80000 {
label = "config";
reg = <0x80000 0x80000>;
read-only;
};
factory: partition@100000 {
label = "factory";
reg = <0x100000 0x40000>;
read-only;
};
partition@140000 {
label = "config2";
reg = <0x140000 0x40000>;
read-only;
};
partition@180000 {
label = "firmware";
compatible = "openwrt,uimage", "denx,uimage";
openwrt,padding = <96>;
reg = <0x180000 0x2800000>;
};
partition@2980000 {
label = "private";
reg = <0x2980000 0x2000000>;
read-only;
};
partition@4980000 {
label = "firmware2";
reg = <0x4980000 0x2800000>;
};
partition@7180000 {
label = "mydlink";
reg = <0x7180000 0x600000>;
read-only;
};
partition@7780000 {
label = "reserved";
reg = <0x7780000 0x880000>;
read-only;
};
};
};
Do you have access to the console? Do you have a bootlog for your device by any chance?
2 Likes
D-Link Model Name: DIR-853 Hardware Version: A2 Firmware Version: 1.20
I access the router through the URL http://192.168.0.1 and inside the console that I access via the Web, I managed to get some log information.
Follow the log below:
2020-07-14 12:55:40 [SYSLOG]: start BusyBox v1.12.1
2020-07-14 12:55:40 [MLD]: mrib_mld_source: failed to detect local source address on 13
2020-07-14 12:55:40 [MLD]: mrib_mld_source: failed to detect local source address on 15
2020-07-14 12:55:40 [MLD]: mrib_mld_source: failed to detect local source address on 16
2020-07-14 12:56:07 [RC]: RC start
total used free shared buffers
Mem: 120980 79256 41724 0 0
Swap: 0 0 0
Total: 120980 79256 41724
PID USER VSZ STAT COMMAND
1 admin 4784 R /sbin/preinit
2 admin 0 SW [kthreadd]
3 admin 0 SW [ksoftirqd/0]
4 admin 0 SW [kworker/0:0]
5 admin 0 SW< [kworker/0:0H]
6 admin 0 SW [kworker/u8:0]
7 admin 0 SW [migration/0]
8 admin 0 SW [rcu_bh]
9 admin 0 SW [rcu_sched]
10 admin 0 SW [migration/1]
11 admin 0 SW [ksoftirqd/1]
12 admin 0 SW [kworker/1:0]
13 admin 0 SW< [kworker/1:0H]
14 admin 0 SW [migration/2]
15 admin 0 SW [ksoftirqd/2]
16 admin 0 SW [kworker/2:0]
17 admin 0 SW< [kworker/2:0H]
18 admin 0 SW [migration/3]
19 admin 0 SW [ksoftirqd/3]
20 admin 0 SW [kworker/3:0]
21 admin 0 SW< [kworker/3:0H]
22 admin 0 SW< [khelper]
23 admin 0 SW [kdevtmpfs]
24 admin 0 SW< [netns]
25 admin 0 SW< [writeback]
26 admin 0 SW< [bioset]
27 admin 0 SW< [kblockd]
28 admin 0 SW [khubd]
29 admin 0 SW [kworker/3:1]
30 admin 0 SW [kworker/2:1]
31 admin 0 SW [kworker/1:1]
32 admin 0 SW [kworker/0:1]
33 admin 0 SW [kswapd0]
34 admin 0 SWN [ksmd]
35 admin 0 SW [fsnotify_mark]
36 admin 0 SW< [crypto]
43 admin 0 SW [kworker/u8:1]
48 admin 0 SW< [deferwq]
49 admin 0 SWN [jffs2_gcd_mtd6]
57 admin 1132 S tw_hotplug
63 admin 5592 S nvram_daemon
439 admin 3972 S stad 1
441 admin 3976 S stad 2
454 admin 4784 S /sbin/preinit
542 admin 944 S nl_server -i br0 -s dlinkrouter -s dlinkrouterEEBA -s
543 admin 932 S nl_server -i br0 -s dlinkrouter -s dlinkrouterEEBA -s
549 admin 1424 S dnsmasq -C /tmp/dnsmasq.conf -6 /tmp/dnsmasq_dhcp_eve
550 admin 1416 S dnsmasq -C /tmp/dnsmasq.conf -6 /tmp/dnsmasq_dhcp_eve
570 admin 4804 S /bin/lighttpd -f /etc_ro/lighttpd/lighttpd.conf -m /e
571 admin 5572 S /bin/prog.cgi
574 admin 1904 S dhcp6s -c /tmp/dhcp6s.conf -k /tmp/dhcp6sctlkey br0
576 admin 1032 S radvd -m none -C /tmp/radvd.conf
584 admin 1700 S syslogd -L
591 admin 980 S omcproxy -e3 eth3 br0 br2 br3 scope=realm
639 admin 0 SW [RtmpCmdQTask]
640 admin 0 SW [RtmpWscTask]
641 admin 0 SW [HwCtrlTask]
642 admin 0 SW [ser_task]
643 admin 0 SW [kworker/1:2]
660 admin 0 SW [RtmpMlmeTask]
709 admin 1464 S bndstrg2 -i ra0 -i rax0
1164 admin 1320 S mDNSResponder -b -i br0 -f /tmp/mdns_resp.conf -e dli
1219 admin 4144 S timer
1847 admin 1704 S sh -c ps >> /etc_ro/lighttpd/www/web/messages
1848 admin 1704 R ps
br0 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BA
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::c6e9:aff:fe4c:eeba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1964 errors:0 dropped:0 overruns:0 frame:0
TX packets:681 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:143648 (140.2 KiB) TX bytes:654412 (639.0 KiB)
br1 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BE
inet addr:192.168.7.1 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::603e:50ff:fe8c:37e5/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:408 (408.0 B)
br2 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BF
inet6 addr: fe80::f4de:acff:fed9:db6c/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:568 (568.0 B)
br3 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:C0
inet6 addr: fe80::f0b2:a7ff:fe31:b11/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:568 (568.0 B)
eth2 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BA
inet6 addr: fe80::c6e9:aff:fe4c:eeba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1741 errors:0 dropped:0 overruns:0 frame:0
TX packets:2805 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:156121 (152.4 KiB) TX bytes:309541 (302.2 KiB)
Interrupt:3
eth2.1 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BA
inet6 addr: fe80::c6e9:aff:fe4c:eeba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:37189 (36.3 KiB)
eth2.2 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BA
inet6 addr: fe80::c6e9:aff:fe4c:eeba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:266 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:37259 (36.3 KiB)
eth2.3 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BA
inet6 addr: fe80::c6e9:aff:fe4c:eeba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:37189 (36.3 KiB)
eth2.4 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BA
inet6 addr: fe80::c6e9:aff:fe4c:eeba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:37189 (36.3 KiB)
eth3 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BD
inet6 addr: fe80::c6e9:aff:fe4c:eebd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:238 (238.0 B) TX bytes:558 (558.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ra0 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BC
inet6 addr: fe80::c6e9:aff:fe4c:eebc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:4
rax0 Link encap:Ethernet HWaddr C4:E9:0A:4C:EE:BB
inet6 addr: fe80::c6e9:aff:fe4c:eebb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2089 errors:0 dropped:0 overruns:0 frame:0
TX packets:938 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:177562 (173.4 KiB) TX bytes:652296 (637.0 KiB)
I cannot access via USB, or serial model does not have this possibility, can I access a web interface via cable or Wireless?
But I sent the logs that I got, can you help me? We bought a lot of this equipment and I need it to work with OpenWRT and I still don't understand where to start..
Thanks, I guess you don't have access to the console. It would have been useful to have a complete bootlog.
Does the device have a recovery function? Can you boot with the reset button pushed in and see if you get a blinking led light please?
Hi @kar200 does have the recovery function.
Turning on the device with the reset pressed, the orange light starts blinking and enters the screen below.
Hello, I'm still researching how to make it work, it seems that the difference between the DIR 853 A3 for my DIR 853 A2 device is the memory, but I don't know how to make the compilation and change this information in the .bin file to test.
You can help me too, I need to make this equipment work DIR 853 A2. Thank you all in advance.
Ok that's good.
Have a look here
You should be able to start a telnet session by just using the browser. you won't get any specific page just an error but the you can try and telnet to the router with admin and your admin password.
If that works it would be better to try and get a full backup of the device. Does the device have usb by the way? From the pictures it seems like it does not. Am I right?
Now the disclaimer
I HAVE COMPILED THIS FIRMWARE WITHOUT MUCH INFO FROM YOUR DEVICE. I HAVE ASSUMED THAT IT IS USING THE SAME PARTITION SCHEME AS THE DIR-878 SO THIS IS WHAT i USED.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
Ok now that's done this is the file. Try and flash it from that web interface. It does not mean it will work the first try.
If it does not I had some success with windows edge in private mode. If that does not work try with curl
curl -v -i -F "firmware=@openwrt-ramips-mt7621-dlink_dir-853-a2-squashfs-factory.bin" 192.168.0.1
This is the file. Please understand that it might brick your router.
2 Likes
HI ads119
as I stated to you on github
you need to capture the full boot log from the serial port inside the router
& I'm sorry but if you don't or can't lookup the basic skills on how to do this
then I'm afrade it's not going to happen you need this serial console access
look up how to connect a USB to TTL level rs232 adapter to you router
1 Like
another thing there is not much info out there for an A2
could you please look at the web interface of you router
look for the model number is it saying DIR-853-A2 or DIR-853-A1
1 Like
Here is the equipment information:
D-Link: DIR-853 Hardware Version: A2 Firmware Version: 1.20
I'll do this procedure you gave me and let you know if it worked.
