linux &
root@DD-WRT:/tmp#
[1]+ Done(255) write tl-wr1043nd-webflash.bin linux
root@DD-WRT:/tmp# mtd write wr1043ndv1_tp_recovery.bin linux
Unlocking linux ...
Could not unlock MTD device: linux
linux: Not supported
Writing from wr1043ndv1_tp_recovery.bin to linux ... [e]Erasing mtd failed: linux
root@DD-WRT:/tmp# \
>
root@DD-WRT:/tmp#
root@DD-WRT:/tmp#
root@DD-WRT:/tmp#
root@DD-WRT:/tmp# wget http://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/04-14
-2023-r52330/tplink_tl-wr1043nd/tl-wr1043nd-webflash.bin
root@DD-WRT:/tmp# write wr1043ndv1_tp_recovery.bin linux
wr1043ndv1_tp_recovery.bin: Bad trx header
root@DD-WRT:/tmp# mtd write wr1043ndv1_tp_recovery.bin linux &
root@DD-WRT:/tmp# Unlocking linux ...
Could not unlock MTD device: linux
linux: Not supported
If I were you, I would stop this nonsense.
You have already entered commands incorrectly several times and tried to flash the wrong firmware with wrong methods.
Connection received from 192.168.0.86 on port 2575 [07/05 20:09:24.696]
Read request for file <wr1043nv1_tp_recovery.bin>. Mode octet [07/05 20:09:24.696]
File <wr1043nv1_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [07/05 20:09:24.711]
Connection received from 192.168.0.86 on port 2575 [07/05 20:09:27.696]
Read request for file <wr1043nv1_tp_recovery.bin>. Mode octet [07/05 20:09:27.711]
File <wr1043nv1_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [07/05 20:09:27.711]
Connection received from 192.168.0.86 on port 2575 [07/05 20:09:30.691]
Read request for file <wr1043nv1_tp_recovery.bin>. Mode octet [07/05 20:09:30.707]
File <wr1043nv1_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [07/05 20:09:30.707]
Connection received from 192.168.0.86 on port 2575 [07/05 20:09:33.702]
Read request for file <wr1043nv1_tp_recovery.bin>. Mode octet [07/05 20:09:33.702]
File <wr1043nv1_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [07/05 20:09:33.702]
Connection received from 192.168.0.86 on port 2575 [07/05 20:09:36.698]
Read request for file <wr1043nv1_tp_recovery.bin>. Mode octet [07/05 20:09:36.698]
File <wr1043nv1_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [07/05 20:09:36.698]
Connection received from 192.168.0.86 on port 2569 [07/05 20:10:45.334]
Read request for file <wr1043nv1_tp_recovery.bin>. Mode octet [07/05 20:10:45.349]
Using local port 55256 [07/05 20:10:45.349]
<wr1043nv1_tp_recovery.bin>: sent 16130 blks, 8258048 bytes in 4 s. 0 blk resent [07/05 20:10:49.218]
important thing is name should be wr1043nv1_tp_recovery.bin
Problem what i have with usb router wr1043v1 is that i love usb routers and its useful to have hard disk in lan access on samba or ftp .. See i need that more than wifi , in some cases hapeng that router just stuck on access on samba, its just if i get lucky i can only reboot via ssh.If not manualu power on than work ... than bad work with lot acces on hard disk please considre that
Thank you friend
Last edited by slowmotionscene on Mon May 08, 2023 13:24; edited 1 time in total
Then buy a proper NAS, the router is not a replacement for it... it has terrible file system handling and very limited functionality.
The mounted USB drives are simply ripped out from the file system and not properly unmounted, the jornal of ext drives is constantly "dirty" and need a recovery ...
...
Who uses such a thing as NAS certainly does not value reliability and data security
It was clear that the option to upgrade to 52330 was to TFTP the factory-to-ddwrt.bin renamed as wr1043nv1_tp_recovery.bin after the normal CLI/WebUI flashing failed with "image too big" and there was no change in file sizes from previous version to 52330. Sorry, absent from class, and because of the language barrier, I was not going to leave any lumps on my pretty forehead trying to explain any further while slamming my head into this granite countertop.
Anyway, you should be able to flash 52330/52369 factory-to-ddwrt.bin from TP-Link firmware and then report any issues or seek help in configuring your network storage functionality properly.
(That should be a fun thread to read later <eyeroll>...) _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
i can now give you report for usb nas what i need for unfortunatly its not good
like 1 2 yeuar before current i try aslo , first was 04-14-2023-r52330 usb was unstabile, on way that all works all plug ins but when i use on routers wifi and access on hard disk on usb nas router will reboot , that happend many times and many builds before i say for 2 yeuars i was go back all same no luck for nas. I also try to change hard disk happand error same, only for usb flash was good but that is not what i need
so i use old build
all that i was testing yesterday after unbrick, but on 2016 build nas is ok
Last edited by slowmotionscene on Mon May 08, 2023 13:22; edited 1 time in total
Joined: 16 Nov 2015 Posts: 6411 Location: UK, London, just across the river..
Posted: Mon May 08, 2023 7:28 Post subject:
do not use NTFS as its not native linux format, try ext2(for thumb drive), 3 or 4 for hard disk.. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 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
NTFS is never a native Linux file system. Also, Paragon NTFS3 implementation has not been updated in 15 months.
NTFS3 is also missing key utilities or tools especially no equivalent or native Linux replacement to Windows chkdsk.
In-kernel Samba or cifsd or ksmbd has not seen any updates for 7 months also ksmbd-tools no changes 9 months.
Anyone who searches knows this or read any build thread, but if everything new is to be backported expect issues.