Joined: 25 Jun 2014 Posts: 142 Location: São Paulo - Brazil
Posted: Fri Oct 20, 2017 0:18 Post subject:
Hi Alozaros, Hi, i'm trying following instructions.. but i stuck here:
Code:
D:\>pscp.exe factory-to-ddwrt.bin root@192.168.1.1:/tmp/factory-to-ddwrt.bin
root@192.168.1.1's password:
sh: /usr/libexec/sftp-server: not found
Fatal: Received unexpected end-of-file from server
before try to upgrade, i reset the tl-wr841ndv11 (r33375), and enable SSHd, both files in same dir, any idea ? thx.
do we have to do this every time we want to upgrade from now on?
bc i downgraded to 33492 from 33555 hoping to be able to use the web-gui to upgrade but still can't
model: tl-wr1043nd_v1.8
-
(edit: update status)
i used it to upgrade to 33607, at least works well
I am having the same problem on the router "TP-Link TL-WR743ND v1"
I can not in any way restore the original firmware or upgrade to the latest firmware, could anyone guide me?
Sorry for the flood, no one can help me with the problem?
I do not know how to find the size of the bootloader, when I go to the string "00020000" it has no name "tp-link", tplink, or dd-wrt ", encounter tp-link just at the beginning of the file.
I use windows and I'm using PuTTY, can I use this one?
I understand little of linux!
the "factory-to-ddwrt.bin" that I will use is "r33375" or the version I want to use?
if anyone can guide me in the commands on windows, I thank
I don't understand your post, probably because of my bad English.
So, did you downgrade the build 33555 into 33492 with success?
If so, why didn't you upgrade with this method to the latest version?
You should use the method described in this thread only if you stuck with build 33375, because webflash from this build is faulty.
Please excuse me if I will say something stupid or wrong.
I do like and follow this topics and technology with How-to and guides, I followed the electronic but did not enter in the programming mode. So networks is a hobby and support for friends
BrainSlayer (thank you so much for your dedication to us)wrote that :
"in older firmwares the string isnt tp-link but dd-wrt. i changed that string to tp-link in that firmware and this all caused the bug since my mtd partition code was looking for the wrong string to detect the bootloader size
"
could it be possible to release a fix that could contain both strings in order to bypass the bootloader size?
Because I believe that the incoming releases may have this fixed, so we just need to cover a few releases that are blocking the upgrade process.
In my case I would like to downgrade for a old version to see if I can solve LAN low speed transfer rate that I am have with a WR941 v3.6 under 33525.
The network is ok, tested with other router and same configs.
Only the 941 on the lan side is "cutted" or appears limited speed like effective QOS
Well.. so maybe we could have a patch to apply and go back to release XXXX that could avoid the advanced tasks for DD-WRT fans but not so experience.
@akynxs scroll down the output with the arrow keys or j/k keys until you reach 00020000 or whatever is the correct offset that contains the tp-link or dd-wrt string.
@akynxs scroll down the output with the arrow keys or j/k keys until you reach 00020000 or whatever is the correct offset that contains the tp-link or dd-wrt string.
Thanks guys for the help
I managed to get out of this bugged firmware
Just to confirm, the router "TP-Link TL-WR743ND v1" = 131072 (bootloader size).
I don't understand your post, probably because of my bad English.
So, did you downgrade the build 33555 into 33492 with success?
If so, why didn't you upgrade with this method to the latest version?
You should use the method described in this thread only if you stuck with build 33375, because webflash from this build is faulty.
I'm not a native english speaker either
About your 1st Q... yes, I did downgrade like you said successfully and then using the same method I upgraded to r33607
2nd Q: I thought reverting to a previous could bring the ability to use the webgui to upgrade like before, but after thinking what I was doing I understood that I was actually reusing the bootsector and injecting it into a firmware without it
btw 33375 is not the only one generating this, there have been reports of other versions doing the same
in older firmwares the string isnt tp-link but dd-wrt. i changed that string to tp-link in that firmware and this all caused the bug since my mtd partition code was looking for the wrong string to detect the bootloader size
Will future dd-wrt firmwares fix this problem or will all those who are effected (can't upgrade/switch back to stock) have to manually fix the problem discussed in this thread?
