Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Thu Aug 22, 2019 5:33 Post subject:
on the recent builds on 3 wrong attempts, you will be banned no GUI for a 10 min, so it will take a long time... _________________ 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
Alright, so I've got the pi all set up and I got the router apart however now I'm having an issue. Everything is all configured correctly however when I power on the router I get no prompt or anything in my minicom window, I cannot tell if maybe the serial pins on the router are not connected right or if the router just doesn't communicate over serial until you ask it to.
I do notice that when I wiggle the wires around that are connected to the router's serial connections I get random characters on the minicom screen which I figure is from random 1's and 0's from the wires moving.
Jan 1 00:00:11 DD-WRT kern.notice kernel: Creating 6 MTD partitions on "bcmsflash":
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000000000-0x000000080000 : "boot"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000080000-0x000000ff0000 : "linux"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000220000-0x000000df0000 : "rootfs"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000df0000-0x000000ff0000 : "ddwrt"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000ff0000-0x000001000000 : "nvram_cfe"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000fe0000-0x000000ff0000 : "nvram"
As you see, on telnet just copy "nvram_cfe" to "nvram" is that all you need.
Code:
mtd erase nvram
mtd write /dev/mtd4 nvram
or
dd if=/dev/mtdblock4 of=/dev/mtdblock5
just remember bk before doing.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Mon Aug 26, 2019 18:45 Post subject:
nckwrn wrote:
Alright, so I've got the pi all set up and I got the router apart however now I'm having an issue. Everything is all configured correctly however when I power on the router I get no prompt or anything in my minicom window, I cannot tell if maybe the serial pins on the router are not connected right or if the router just doesn't communicate over serial until you ask it to.
I do notice that when I wiggle the wires around that are connected to the router's serial connections I get random characters on the minicom screen which I figure is from random 1's and 0's from the wires moving.
There are no labels on the router board for the serial connections.
Look at the pictures really closely. That document tells you exactly the order of the pins. You probably have loose connections, specifically the ground connection. If putty, minicom, whatever client you are using is connected and configured correctly, it shouldn't be giving you a problem.
You could try tftp flashing the stock firmware or latest build a la recovering from a bad flash, if you can get that to work. You WILL want to pay close attention to the C9 wiki as far as what IP address to push the file to.
Jan 1 00:00:11 DD-WRT kern.notice kernel: Creating 6 MTD partitions on "bcmsflash":
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000000000-0x000000080000 : "boot"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000080000-0x000000ff0000 : "linux"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000220000-0x000000df0000 : "rootfs"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000df0000-0x000000ff0000 : "ddwrt"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000ff0000-0x000001000000 : "nvram_cfe"
Jan 1 00:00:11 DD-WRT kern.notice kernel: 0x000000fe0000-0x000000ff0000 : "nvram"
As you see, on telnet just copy "nvram_cfe" to "nvram" is that all you need.
Code:
mtd erase nvram
mtd write /dev/mtd4 nvram
or
dd if=/dev/mtdblock4 of=/dev/mtdblock5
just remember bk before doing.
The problem with telnet is it asks for a password that I can't figure out.
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Thank you everyone for the help, will update on progress.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Mon Aug 26, 2019 21:44 Post subject:
nckwrn wrote:
deslatha wrote:
As you see, on telnet just copy "nvram_cfe" to "nvram" is that all you need.
Code:
mtd erase nvram
mtd write /dev/mtd4 nvram
or
dd if=/dev/mtdblock4 of=/dev/mtdblock5
just remember bk before doing.
The problem with telnet is it asks for a password that I can't figure out.
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Thank you everyone for the help, will update on progress.
He tends to chime in with something that completely overlooks the rest of the thread. At least this time, his english wasn't horribly broken?
Ok, I am guessing you didn't solder a header or wires into your pc board. Not always ideal, because you need a good connection. Trust me, that is probably a large part of the problem
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Yes, they should be soldered; the trace connection is on the plane of the board, not the bore of the hole. If you must instead utilize a press fit, have a helper to prevent intermittent connections. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Aug 27, 2019 0:32 Post subject:
jwh7 wrote:
nckwrn wrote:
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Yes, they should be soldered; the trace connection is on the plane of the board, not the bore of the hole. If you must instead utilize a press fit, have a helper to prevent intermittent connections.
^ I kinda left out the obvious in my previous comment. On a side note, I am waiting to see when the E2500 v4 GPL hits the public. I was going to say I was curious about the hardware, but someone apparently has already picked one up and cracked it open, and it is MediaTek:
Maybe the code will be a little easier to walk through and fix. Maybe not. They may not even release a GPL, seems like none of the *updated* MediaTek stuff from Linksys/Belkin was available, last I looked.
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Yes, they should be soldered; the trace connection is on the plane of the board, not the bore of the hole. If you must instead utilize a press fit, have a helper to prevent intermittent connections.
I just don't trust my soldering skills enough to work on such tight tolerances.
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Yes, they should be soldered; the trace connection is on the plane of the board, not the bore of the hole. If you must instead utilize a press fit, have a helper to prevent intermittent connections.
I just don't trust my soldering skills enough to work on such tight tolerances.
It’s not as difficult as you think. You are scaring yourself. _________________ I am far from a guru, I'm barely a novice.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Aug 28, 2019 2:12 Post subject:
Malachi wrote:
nckwrn wrote:
jwh7 wrote:
nckwrn wrote:
I will try serial recovery again today, maybe use a little aluminum foil to make the jumper pins more solid in the router's serial holes.
Yes, they should be soldered; the trace connection is on the plane of the board, not the bore of the hole. If you must instead utilize a press fit, have a helper to prevent intermittent connections.
I just don't trust my soldering skills enough to work on such tight tolerances.
It’s not as difficult as you think. You are scaring yourself.
X2. My hands aren't as steady as they used to be, my eyesight is sh*t, and I've installed pins on all of my E4200 v1s and on my E2500 v3. I used a magnifying glass to be able to see what the hell I was doing and my iron has led lights.
So I finally soldered leads onto the PCB and connected it to the USB Uart adapter however I cannot access the cfg.
Basically if I power on the router with the serial connection open and the UART connected, the router doesn't boot up. However if I start the router with the UART adapter not plugged in, the router boots like normal and eventually the serial connection opens and asks for my ddwrt password and username.
I've tried holding ctrl c while plugging the router in and it simply doesnt seem to do anything if the serial connection is open while the router is powered on.
if I power on the router with the serial connection open and the UART connected, the router doesn't boot up. However if I start the router with the UART adapter not plugged in, the router boots like normal and eventually the serial connection opens and asks for my ddwrt password and username.
I've tried holding ctrl c while plugging the router in and it simply doesnt seem to do anything if the serial connection is open while the router is powered on.
This part is confusing:
>eventually the serial connection opens and asks for my ddwrt password and username
Is this after you've booted it w/o serial connected, then you plug it in after boot? Or are you talking about telnet/ssh or something?
Otherwise, it sounds like an adapter or connection/solder issue. What adapter are you using, and what pins did you connect?
You must have working serial at power-up in order for ctrl-C to break CFE. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
if I power on the router with the serial connection open and the UART connected, the router doesn't boot up. However if I start the router with the UART adapter not plugged in, the router boots like normal and eventually the serial connection opens and asks for my ddwrt password and username.
I've tried holding ctrl c while plugging the router in and it simply doesnt seem to do anything if the serial connection is open while the router is powered on.
This part is confusing:
>eventually the serial connection opens and asks for my ddwrt password and username
Is this after you've booted it w/o serial connected, then you plug it in after boot? Or are you talking about telnet/ssh or something?
Otherwise, it sounds like an adapter or connection/solder issue. What adapter are you using, and what pins did you connect?
I only get a response from the serial connection when I plug the adapter in after letting the router boot. When it boots the prompt says DDWRT Login and asks for a username and then password.
I got an ebay "USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter AD" and I soldered 3 wires to the router PCB, TX, RX, and GRND. TX is the square hole, RX is next to TX, and GRND is next to RX. I connected the soldered wires to the serial adapter making sure to reverse the TX and RX pins.
