DD-WRT :: View topic - PROBLEMS WITH UPGRADE/DOWNGRADE from build 33375 (SOLVED)

PROBLEMS WITH UPGRADE/DOWNGRADE from build 33375 (SOLVED)

This topic is locked: you cannot edit posts or make replies.

DD-WRT Forum Index -> Atheros WiSOC based Hardware

Goto page Previous 1, 2, 3, 4, 5, 6, 7, 8, 9 Next

View previous topic :: View next topic

Author

Message

alfon_sico
DD-WRT Novice

Joined: 28 Feb 2014
Posts: 13

Posted: Sun Jan 21, 2018 16:22 Post subject:

rscm wrote:

eladb wrote:

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:

> root@DD-WRT:~# cat /proc/mtd

> dev: size erasesize name
> mtd0: 00040000 00010000 "RedBoot"
> mtd1: 007a0000 00010000 "linux"
> mtd2: 006ae000 00010000 "rootfs"
> mtd3: 00030000 00010000 "ddwrt"
> mtd4: 00010000 00010000 "nvram"
> mtd5: 00010000 00010000 "FIS directory"
> mtd6: 00010000 00010000 "board_config"
> mtd7: 00800000 00010000 "fullflash
> root@DD-WRT:~# dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072

> 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!

btw in my case i wrote the boot.bin in a linux machine (my desktop) because the router didn't have enough space to handle all the operation
i got the dump and then "scp-it" from the router, used the firmware and cat command on it and then i trasfered it back to the router. that way i could bypass the free space issue

are you sure you don't have response? ping? access via ssh/telnet? have you hard-reset it? there's plenty to test before thinking on serial cables or flash chips

ps:
i did brick my router in the past and saved it, bc of that i have cables and pins attached to the port that way in the future i could connect the serial ttl usb adapter easy

Maybe this is my problem.. I cant finish cat order. Takes several minutes and when push enter then got ampn out connection

My router is tp link
I have a mac but i could virtualize linux or windows on it
For now
- telnet router
- wget firmware factory to ddwrt (why it cant be the normal upgrade firm?)
- dd boot7 as boot.bin
- stuck when cat firmware at boot.bin

Could it be because is out of space?
Could it be because it needs more time (>5 mins?)

How I would manage linux terminal for transfer files with the router?
Could I do with mac terminal?

Sponsor

MWisBest
DD-WRT Novice

Joined: 26 Sep 2013
Posts: 13

Posted: Mon Jan 22, 2018 17:55 Post subject:

This is still an issue on the TP-Link TL-WR1043ND v1. Flashed r34311 (12/29/17), can't upgrade via the web interface to r34578 (01/19/18).

As BrainSlayer mentioned, builds before r33375 (09/19/17) used "DD-WRT" as the string at the start of the firmware, and since that build they're all using "TP-LINK Technologies".

Relates to these changes:
http://svn.dd-wrt.com/changeset/33356
http://svn.dd-wrt.com/changeset/33357

This change was supposed to fix it...
http://svn.dd-wrt.com/changeset/33405

but it was not applied to ar7100_flash.c as well
http://svn.dd-wrt.com/browser/src/linux/universal/linux-3.10/drivers/mtd/devices/ar7100_flash.c

alfon_sico
DD-WRT Novice

Joined: 28 Feb 2014
Posts: 13

Posted: Tue Jan 23, 2018 13:10 Post subject:

MWisBest wrote:

This is still an issue on the TP-Link TL-WR1043ND v1. Flashed r34311 (12/29/17), can't upgrade via the web interface to r34578 (01/19/1 Cool

.

As BrainSlayer mentioned, builds before r33375 (09/19/17) used "DD-WRT" as the string at the start of the firmware, and since that build they're all using "TP-LINK Technologies".

Relates to these changes:
http://svn.dd-wrt.com/changeset/33356
http://svn.dd-wrt.com/changeset/33357

This change was supposed to fix it...
http://svn.dd-wrt.com/changeset/33405

but it was not applied to ar7100_flash.c as well
http://svn.dd-wrt.com/browser/src/linux/universal/linux-3.10/drivers/mtd/devices/ar7100_flash.c

So, I'm at Firmware: DD-WRT v3.0-r33607 std (10/25/17)
I can't upgrade or downgrade
I can't use SSH (gray) but Telnet
It seems I'm semi bricked

alfon_sico
DD-WRT Novice

Joined: 28 Feb 2014
Posts: 13

Posted: Tue Jan 23, 2018 13:19 Post subject:

Sorry, I get file "factory-to-ddwrt"+ mtdblock7 for tplink a 8192000bytes file

So i'm ready to do mtd -f write boot.bin fullflash

Two questions before
- Will I loose my personal configuration?
I'm doing a upgrade (stuck at versión greater than 34578 for upgrade to the newest.
- Could I downgrade to a previous 34578 version using the same method?

I’d like downgrade to 7-2-2017 version that works great for me

arvinp
DD-WRT Novice

Joined: 15 Mar 2010
Posts: 6

Posted: Wed Jan 24, 2018 17:11 Post subject:
Can someone please make a youtube video showing how to do all these steps to fix the problem.

alfon_sico
DD-WRT Novice

Joined: 28 Feb 2014
Posts: 13

Posted: Wed Jan 24, 2018 22:38 Post subject:

I think all was mess up but like a miracle it works

TP Link 1043ND 1.8
Telnet

* dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072
* wget http://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/01-19-2018-r34578/tplink_tl-wr1043nd/factory-to-ddwrt.bin
* cat factory-to-ddwrt.bin >> boot.bin
* (DEEP BREATH) mtd -f write boot.bin fullflash
Unlocking fullflash ...
Could not unlock MTD device: fullflash
fullflash: Not supported
Writing from boot.bin to fullflash ... [w/e]
GLUP** (Not supported?)(not unlock?) I read this forum and find a user with boot loop

* reboot
Segmentation fault
Segmentation fault
-sh: /tmp/.rc_shutdown: Permission denied
-sh: /sbin/reboot: I/O error
SUPER GLUP**!!
* ls
Segmentation fault

Power off router and pray ... wait ... boot ... leds.... wlan ... led ...URL and got it with 34578 version and old config maintained

Alozaros
DD-WRT Guru

Joined: 16 Nov 2015
Posts: 6436
Location: UK, London, just across the river..

Posted: Thu Jan 25, 2018 6:55 Post subject:

Writing from boot.bin to fullflash ... [w/e]

at this moment you have to wait !!!
give it 10 min to be sure....

all its ok after that...
_________________
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

alfon_sico
DD-WRT Novice

Joined: 28 Feb 2014
Posts: 13

Posted: Sun Jan 28, 2018 8:02 Post subject:
Si, this massages are normal during update? “Could not unlock MTD device: fullflash fullflash: Not supported ” “Segmentation fault” “Permission denied“ “I/O error” I want to try a downgrade but I’m a little scary about that even when I upgrade successfully Could I try doing through web Gui?

wilhelmo
DD-WRT Novice

Joined: 30 Jan 2018
Posts: 1

Posted: Tue Jan 30, 2018 14:19 Post subject:
I tried the workaround to update my Archer C5 v1 from r33375 to a newer. update successfully! thx4help!

rafalB
DD-WRT Novice

Joined: 02 Oct 2015
Posts: 19

Posted: Fri Feb 02, 2018 18:29 Post subject:

My story with upgarde is as follow.
I'm running TP-Link 1043ND v1 version r33679 (11/04/2017)
Steps I did:

A)
root@tp-link:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "RedBoot"
mtd1: 007a0000 00010000 "linux"
mtd2: 006bf000 00010000 "rootfs"
mtd3: 00020000 00010000 "ddwrt"
mtd4: 00010000 00010000 "nvram"
mtd5: 00010000 00010000 "FIS directory"
mtd6: 00010000 00010000 "board_config"
mtd7: 00800000 00010000 "fullflash"

B)
root@tp-link:~#dd if=/dev/mtdblock7 | hexdump -C | less

and then I scrolled down to the line 00020000 where I can see:

00020000 01 00 00 00 54 50 2d 4c 49 4e 4b 20 54 65 63 68 |....TP-LINK Tech|

which means botloader size is 131072 (=20000 Hex)

C)
Then I have copied latest factory-to-ddwrt.bin to /tmp by launching the command on my Windows 7 machine:

pscp -scp c:\temp\factory-to-ddwrt.bin root@192.168.1.1:/tmp/factory-to-ddwrt.bin

And using WinSCP I see factory-to-ddwrt.bin file (7872 KB) is present in /tmp directory

D)
root@tp-link:~#dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072

And using WinSCP I see boot.bin file (128 KB) is present in /tmp directory

root@tp-link:~#cd /tmp

E)
root@tp-link:~#cat factory-to-ddwrt.bin >> boot.bin

And this command is running for 5-10 seconds, router is restarted and both files are not present in /tmp folder

Do I understand that something is wrong and I should not go for the command "mtd -f write boot.bin fullflash" because it simple doesn't exist?
Question is why router is restarting at step E) ?

tzok
DD-WRT User

Joined: 10 Aug 2011
Posts: 67

Posted: Mon Feb 05, 2018 21:08 Post subject:

alfon_sico wrote:

I've just killed my router by following this. It is missing the correct path! Should be:
dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072
wget http://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/01-31-2018-r34777/tplink_tl-wr1043nd/factory-to-ddwrt.bin
cat factory-to-ddwrt.bin >> /tmp/boot.bin
mtd -f write /tmp/boot.bin fullflash

Without this /tmp/ (or cd /tmp/) this will irreversibly brick your router!

hokuto
DD-WRT Novice

Joined: 05 Apr 2016
Posts: 20

Posted: Wed Feb 07, 2018 16:37 Post subject:
I was trying this method and ... 1. The ssh connection disconnected midway 2. I waited for a few minutes 3. I turned it off then on 4. The router keeps flashing all 4 lan port lights Did I just brick my router for good?

tzok
DD-WRT User

Joined: 10 Aug 2011
Posts: 67

Posted: Wed Feb 07, 2018 17:49 Post subject:
If it is flashing it means that the U-Boot is still there.

hokuto
DD-WRT Novice

Joined: 05 Apr 2016
Posts: 20

Posted: Thu Feb 08, 2018 1:49 Post subject:

tzok wrote:

If it is flashing it means that the U-Boot is still there.

I forgot to mention that I had TP-Link 1043ND v1.3 (or v1.4, I forgot)

In this case, would the safest option be 30/30/30 then go for tftp, and if not followed by serial recovery?

tzok
DD-WRT User

Joined: 10 Aug 2011
Posts: 67

Posted: Thu Feb 08, 2018 20:58 Post subject:
I had no luck with TFTP recovery, only serial+TFTP... you may do factory reset from serial console, so there is no need for 30+30+30.

Goto page Previous 1, 2, 3, 4, 5, 6, 7, 8, 9 Next

Display posts from previous:

Page 5 of 9

DD-WRT Forum Index -> Atheros WiSOC based Hardware

All times are GMT

Navigation

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Log in

PROBLEMS WITH UPGRADE/DOWNGRADE from build 33375 (SOLVED)

Quick Links

Log in