Joined: 16 Nov 2015 Posts: 6446 Location: UK, London, just across the river..
Posted: Thu Nov 09, 2017 6:19 Post subject:
nope you have to manually fix it if you want to upgrade...
once you fix it, it will be ok to update to new builds... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
I'm having problems with getting this to work, maybe the directions aren't clear enough for me or I'm doing something wrong. A video tutorial would really help me out I think.
Using:
Windows 10 Pro 64bit, PuTTY 64bit, TL-WDR4300 v1 (using 131072), router currently stuck on v3.0-r33375 std (09/19/17).
On PC:
pscp.exe -scp factory-to-ddwrt.bin root@192.168.0.1:/tmp/factory-to-ddwrt.bin
This successfully transferred the full binary.
Then in PUTTY SSH:
dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072
131072+0 records in
131072+0 records out
cd /tmp
cat factory-to-ddwrt.bin >> boot.bin
...and here the router no longer responded.
There are no flashing LEDs, only the power LED.
It is now dead !!!!
I have since tried to establish a serial connection with the router as described here:
Joined: 16 Nov 2015 Posts: 6446 Location: UK, London, just across the river..
Posted: Wed Nov 15, 2017 5:12 Post subject:
well, have you checked and confirmed that your boot size is 131072...
I can already see different output in cat /proc/mtd
if you didn't identify the correct size and 131072 its wrong
it could be bricked already _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
@eladb @Alozaros I don't see how/why it would be bricked from just the steps described since nothing was written back to fullflash yet. All the writing was done to files in tmp. Assuming no typos.
Joined: 09 Feb 2008 Posts: 54 Location: Melbourne, Australia
Posted: Wed Nov 15, 2017 6:01 Post subject:
RSCM has the same router and version and since his "cat /proc/mtd" command gave the same results as mine (mtd7 = fullflash), I assumed my bootloader size was also 131072 as shown below:
> i got 131072 using a hexeditor from a dump of mtd7 (read above @epsilon) (wr1043nd_v1.8 )
I don't understand why it's bricked either since as fizkz pointed out, "nothing was written back to fullflash yet. All the writing was done to files in tmp. Assuming no typos"...there weren't any!
So, maybe you had had a hardware problem, not with software. In this case, it could be something else. Ask for help some electronic engineer. And I'm not sure if it worth to pay for reparing your router. You may check yet, if your power supply adaptor is working correct. Connect your router to another power supply adaptor.
Posted: Thu Nov 16, 2017 17:04 Post subject: U-Boot
The flash chip will need to be flashed with a working version of U-boot compatible with that router. This may require a flash programmer (SPI programmer) but it may be able to be done via JTAG.
If it is truly the flash chip, just buy a new router.
Joined: 09 Feb 2008 Posts: 54 Location: Melbourne, Australia
Posted: Fri Nov 17, 2017 21:59 Post subject:
Thanks team for your suggestions.
The power supply is fine. I've also checked all the DC rails on the router main board +12V, +5V, +3.3V, +2.5V, 1.2V and they all seem correct so I think all the Vregs are good.
I am an electronic engineer.
Interestingly, after being powered up for a long time, all chips are still stone cold! I might try and check the 2 crystal oscillators, 40Mhz & 25MHz, to ensure that they're still working!
I've tried all the methods described on OpenWRT without success. 30/30/30 reset has no effect. All ethernet ports are down and the serial interface on the main board is down. Only the power led is on. No blinking leds.
If I have to replace the flash chip, is the 128KB bootloader rom image all that's needed to be able to re-establish tftp comms with the router?
I understand that this bootloader image would have to be flashed in using JTAG.
Anyone know where I can find the 128KB bootloader rom image for THE TP-Link TL-WR1043N(D) V1.8 ?