DD-WRT :: View topic - New Build - 10/10/2017

New Build - 10/10/2017 - r33492

DD-WRT Forum Index -> Atheros WiSOC based Hardware

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

View previous topic :: View next topic

Author

Message

Alozaros
DD-WRT Guru

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

Posted: Fri Oct 13, 2017 5:57 Post subject:

bleho wrote:

Just updated two wr841nd v9 and v12 (both r33375) to r33492 via ssh as descibed by BS here: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=1098147#1098147

this suits for wr841nd, it is not necessary to check /proc/mtd and bootloader size in this case.

sadly im still unable to proceed as my unit is different, i'm open to any advises, already tried TFTP not working...
and i can't find the correct size for that unit TP-Link TL-1043ND v2 please help ....
Thanks in advance...

that's the output from: dd if=/dev/mtdblock6 | hexdump -C | less

00000000 10 00 00 ff 00 00 00 00 10 00 00 fd 00 00 00 00 |................|
00000010 10 00 01 a6 00 00 00 00 10 00 01 a4 00 00 00 00 |................|
00000020 10 00 01 a2 00 00 00 00 10 00 01 a0 00 00 00 00 |................|
00000030 10 00 01 9e 00 00 00 00 10 00 01 9c 00 00 00 00 |................|
00000040 10 00 01 9a 00 00 00 00 10 00 01 98 00 00 00 00 |................|
00000050 10 00 01 96 00 00 00 00 10 00 01 94 00 00 00 00 |................|
00000060 10 00 01 92 00 00 00 00 10 00 01 90 00 00 00 00 |................|
00000070 10 00 01 8e 00 00 00 00 10 00 01 8c 00 00 00 00 |................|
00000080 10 00 01 8a 00 00 00 00 10 00 01 88 00 00 00 00 |................|
00000090 10 00 01 86 00 00 00 00 10 00 01 84 00 00 00 00 |................|
000000a0 10 00 01 82 00 00 00 00 10 00 01 80 00 00 00 00 |................|
000000b0 10 00 01 7e 00 00 00 00 10 00 01 7c 00 00 00 00 |...~.......|....|
000000c0 10 00 01 7a 00 00 00 00 10 00 01 78 00 00 00 00 |...z.......x....|
000000d0 10 00 01 76 00 00 00 00 10 00 01 74 00 00 00 00 |...v.......t....|
000000e0 10 00 01 72 00 00 00 00 10 00 01 70 00 00 00 00 |...r.......p....|
000000f0 10 00 01 6e 00 00 00 00 10 00 01 6c 00 00 00 00 |...n.......l....|
00000100 10 00 01 6a 00 00 00 00 10 00 01 68 00 00 00 00 |...j.......h....|
00000110 10 00 01 66 00 00 00 00 10 00 01 64 00 00 00 00 |...f.......d....|
00000120 10 00 01 62 00 00 00 00 10 00 01 60 00 00 00 00 |...b.......`....|
00000130 10 00 01 5e 00 00 00 00 10 00 01 5c 00 00 00 00 |...^.......\....|
00000140 10 00 01 5a 00 00 00 00 10 00 01 58 00 00 00 00 |...Z.......X....|
00000150 10 00 01 56 00 00 00 00 10 00 01 54 00 00 00 00 |...V.......T....|
00000160 10 00 01 52 00 00 00 00 10 00 01 50 00 00 00 00
_________________
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

Last edited by Alozaros on Fri Oct 13, 2017 10:56; edited 1 time in total

Sponsor

IgorZ
DD-WRT Novice

Joined: 25 Aug 2017
Posts: 5

Posted: Fri Oct 13, 2017 8:24 Post subject:
Router Model: dir-615 e4 Still does not work web gui firmware upgrade.

overmaxx
DD-WRT Novice

Joined: 21 Dec 2012
Posts: 6

Posted: Fri Oct 13, 2017 10:05 Post subject:
Hi. web gui upgrade not working. How i can upgrade from 3375 to this release?

KuroiTsuki
DD-WRT Novice

Joined: 10 May 2017
Posts: 25

Posted: Fri Oct 13, 2017 10:42 Post subject:

BrainSlayer wrote:

sure. no problem. but you need to know the bootloader size which is different for many devices. so here is a sample for a device with a 128 kb bootloader (you can find out the bootloader size by dumping the fullflash partition and looking for kernel start with a hex editor. the offset of the kernel/firmware is the size of the bootloader.
the following sample assumes that /dev/mtdblock6 is the fullflash partition. so check /proc/mtd before starting

1.
enable ssh on your device
2.
copy factory-to-ddwrt.bin to /tmp
3
dd if=/dev/mtdblock6 of=/tmp/boot.bin bs=1 count=131072
4.
cd /tmp
cat factory-to-ddwrt.bin >> boot.bin
5
mtd -f write boot.bin fullflash
6.
reboot

Man, you really need something more detailed about how to dump full flash partition and how to identify kernel start in that.

Mile-Lile
DD-WRT Guru

Joined: 24 Feb 2013
Posts: 1634
Location: Belgrade

Posted: Fri Oct 13, 2017 11:13 Post subject:

I would try it like this:

check here if your tp-link router is supported (here you can findout the bootloader size):

https://github.com/pepe2k/u-boot_mod

download u-boot for your router from here http://projects.dymacz.pl/?dir=u-boot_mod

Rename the file to uboot.bin and upload the file via scp (enable sshd) to the routers /tmp

then

Code:

mtd write -f /tmp/uboot.bin uboot

this modified uboot has webserver...
hold reset button while powering router and after 4 sec release it... set static IP on your PC to 192.168.1.2...
on Chrome enter http://192.168.1.1/index.html and you can install factory-to-ddwrt...

nekromantik
DD-WRT Novice

Joined: 12 Aug 2017
Posts: 28

Posted: Fri Oct 13, 2017 11:52 Post subject:

tatsuya46 wrote:

nekromantik wrote:

Anyone else on this build and Netgear R7800 got issues with 5ghz WiFi on channel 52+ breaks all AC clients?
None of my clients can connect to the 5ghz AP until I put the channel to 48 or lower.

works. ur devices dont support dfs channels (which is 52-144)

Not true.
Running Stock and LEDE all my AC devices connect to 52 to 60 fine. Only on DD WRT recent builds they cant.

Alozaros
DD-WRT Guru

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

Posted: Fri Oct 13, 2017 12:33 Post subject:

Mile-Lile wrote:

Code:

mtd write -f /tmp/uboot.bin uboot

well, TP-link WR1043NDv2 is not supported, nor my device has TFTPd running, for some odd reason....
tried it so many times even on 2 different PC's in case of..., but still no success... TFTPd on this unit was ok back in the days...
otherwise thanks for this links i can use this method for other devices....in the future...
_________________
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

Last edited by Alozaros on Fri Oct 13, 2017 12:41; edited 1 time in total

mrjcd
DD-WRT Guru

Joined: 31 Jan 2015
Posts: 6293
Location: Texas

Posted: Fri Oct 13, 2017 12:40 Post subject:

nekromantik wrote:

tatsuya46 wrote:

nekromantik wrote:

Anyone else on this build and Netgear R7800 got issues with 5ghz WiFi on channel 52+ breaks all AC clients?
None of my clients can connect to the 5ghz AP until I put the channel to 48 or lower.

works. ur devices dont support dfs channels (which is 52-144)

Not true.
Running Stock and LEDE all my AC devices connect to 52 to 60 fine. Only on DD WRT recent builds they cant.

For best results with those channel probably should use:
VHT80
64 LL
52 UU

HT40
64 lower
60 upper
56 lower
52 upper

I'm using an EA8500 -
My devices work fine on AC/N Mixed or AC only with other combinations of those channels just
fine but I believe there is actually a proper way they should be set Cool

EDIT:
I also know some clients just don't see many 5GHz channels Rolling Eyes

nekromantik
DD-WRT Novice

Joined: 12 Aug 2017
Posts: 28

Posted: Fri Oct 13, 2017 13:42 Post subject:

mrjcd wrote:

nekromantik wrote:

tatsuya46 wrote:

nekromantik wrote:

Anyone else on this build and Netgear R7800 got issues with 5ghz WiFi on channel 52+ breaks all AC clients?
None of my clients can connect to the 5ghz AP until I put the channel to 48 or lower.

works. ur devices dont support dfs channels (which is 52-144)

Not true.
Running Stock and LEDE all my AC devices connect to 52 to 60 fine. Only on DD WRT recent builds they cant.

EDIT:
I also know some clients just don't see many 5GHz channels Rolling Eyes

Yeah but in my instance its not the clients as on LEDE on channel 60 and 56 all my clients connect fine. Main reason of switching back to DD WRT was wifi speeds have less latency on here but then I cant use any DFS channels as something is causing clients to not connect.

Vid0
DD-WRT Novice

Joined: 13 Oct 2017
Posts: 4

Posted: Fri Oct 13, 2017 14:39 Post subject:

Alozaros wrote:

I can confirm TL-1043ND v2 bootloader size is 131072 (0x20000), so all BrainSlayer's commands are valid for this router.

To upload an image I've used pscp.exe (an SCP client, i.e. command-line secure file copy):

pscp.exe <LocalFilePath> <user>@<RemoteHost>:<RemoteDirectory>

pscp.exe factory-to-ddwrt.bin root@192.168.0.254:/tmp/factory-to-ddwrt.bin

Last edited by Vid0 on Fri Oct 13, 2017 19:03; edited 1 time in total

KuroiTsuki
DD-WRT Novice

Joined: 10 May 2017
Posts: 25

Posted: Fri Oct 13, 2017 15:26 Post subject:

Vid0 wrote:

Alozaros wrote:

I can confirm TL-1043ND v2 bootloader size is 131072 (0x2000), so all BrainSlayer's commands are valid for this router.

To upload an image I've used pscp.exe (an SCP client, i.e. command-line secure file copy):

pscp.exe <LocalFilePath> <user>@<RemoteHost>:<RemoteDirectory>

pscp.exe factory-to-ddwrt.bin root@192.168.0.254:/tmp/factory-to-ddwrt.bin

How exactly did you find out the size of the bootloader?

Vid0
DD-WRT Novice

Joined: 13 Oct 2017
Posts: 4

Posted: Fri Oct 13, 2017 15:40 Post subject:

KuroiTsuki wrote:

How exactly did you find out the size of the bootloader?

I've put into boot.bin more than 128kb of data, downloaded it to PC, opened it in hex editor and searched for same bytes that are at the start of factory-to-ddwrt.bin file. Found them at 0x20000 address (TPLINK WR1043ND v2).

Last edited by Vid0 on Fri Oct 13, 2017 19:14; edited 1 time in total

Alozaros
DD-WRT Guru

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

Posted: Fri Oct 13, 2017 16:06 Post subject:

still no success
Unlocking fullflash ...
Could not unlock MTD device: fullflash
fullflash: Not supported
Writing from boot.bin to fullflash ... [w]
and reboot and still on 33375
_________________
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

KuroiTsuki
DD-WRT Novice

Joined: 10 May 2017
Posts: 25

Posted: Fri Oct 13, 2017 16:09 Post subject:
0x2000 is 8kb though, I guess you meant 0x20000 which is 128kb. This seems to be the case for Archer v2 as well. Having same problem as Alozaros though (being unable to unlock, etc) but it actually rebooted with 33492

bdg2
DD-WRT User

Joined: 18 Apr 2013
Posts: 319

Posted: Sat Oct 14, 2017 1:00 Post subject:

KuroiTsuki wrote:

0x2000 is 8kb though, I guess you meant 0x20000 which is 128kb.
This seems to be the case for Archer v2 as well.

Having same problem as Alozaros though (being unable to unlock, etc) but it actually rebooted with 33492

I'm very confused.

Is everyone using b to mean bytes?

It should be B for bytes and b means bits.

128KB seems huge for a bootloader, but maybe it includes some unmapped and/or unused space.

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

Display posts from previous:

Page 5 of 8

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

New Build - 10/10/2017 - r33492

Quick Links

Log in