It copies to mem (which is why the general flashing guide is to reset first, to reduce mem usage), stops writes, flashes, then reboots. Best case is it just boots back to what you already had. Some routers put board_data or nvram partitions -after- the linux partition. And if they don't check the size, you can overwrite and brick.
macexperts wrote:
the worse problem is the cpu runs at boiling temperate - it's been operating this way
The boiling point of water I hope, and not of silicon. Is it really at 100degC? That would be damn hot. ARM routers commonly run 60-85degC, which is ~technically fine (for the warranty period) if their SoC's are rated for it, but it certainly doesn't help the longevity of the silicon and electron paths in the SoC. Not sure what limit the BCM47081A0 is rated. _________________ #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
LOL, yes Very close to the boiling point of water not silicon -around 98.7 98.8 C etc.
Many OEM manufacturing processes do a poor job of lining up the thermal pads and/or the heatsinks themselves. Take a look at the FCC internal photos from the wikidevi FCC link to see what you're working with. Resetting the heatsink w/ better (or more) TIM might make a big difference (or adding or expanding ventilation holes). I've been meaning to do this to my EA6900 for this very reason; it's prone to not have the TIM lined up well. But it's not running 99degC either. _________________ #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
I would have been skeptical if someone told me a chip was running at this temperature without issues. The radios report 50 to 55C on average - much much lower. I appreciate all your feedback, - I saw the other posts on the poorly implemented thermal tape and maybe I'll get around to messing with it sometime and possibly cutting the case some to try to get more direct ventillation. That dual antenna mod with fan looked great also. Mine is a duct tape special at present but it did cool it some at least
I'm not sure it's going to matter in the long run. They had to have had engineering samples and seen that they were running at this high temp right? At least I would assuem that would be the case before going to a full production run. The fact that it's been running so long w/o 'apparent' issues is another indicator that perhaps it's just OK for these chips?
All the best
PS: I forgot that I had underclocked it to 600mhz - I had lowered it intending to see if that dropped the temps and just realized I'd left it the other day - I returned it back to 800mhz with no increase in heat so underclocking doesn't seem to do much for this particular chip (in my case at least).
PS: I forgot that I had underclocked it to 600mhz - I had lowered it intending to see if that dropped the temps and just realized I'd left it the other day - I returned it back to 800mhz with no increase in heat so underclocking doesn't seem to do much for this particular chip (in my case at least).
Or the underclock didn't work; many router models have locked CPU speeds. Did you check in dmesg or `cat /proc/cpuinfo` that it actually took? _________________ #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
Posted: Sat May 19, 2018 9:26 Post subject: TEW-811DRU backup CFE?
I somehow managed to bork the bootloader on this device and failed to make a backup. I have a ch341a programmer and tried using a cfe for similar hardware (linksys ea6350) and was able to write it to the flash, now when it boots I at least get this over serial:
Code:
Digital core power voltage set to 0.9375V
Decompressing...error 1
Would any of you kind souls be willing to share a copy of your cfe.bin so I can bring this back to life?
Just to let you guys know. I pulled out the 'spare' unit 811 I had with same firmware and settings as my unit that runs at nearly 100C without any fan help. The spare runs around 75C to 80C but performance between the two units is the same.
I've found a very unstable release.
Wifi 2.4Ghz crash and It's unstable. Internet download speed it's very slow (1/2 Mbit vs 7/9 with other access point)
I've added a VLAN
VLAN 2 <-- wan port 192.168.1.x
VLAN 3 <-- lan port 5, unbridged, 192.168.100.x with dhcp
VLAN 1 <-- other lan ports & Wifi, 192.168.99.x with BR0
Is there any stable release or this router it's crappy?
I've found a very unstable release.
Wifi 2.4Ghz crash and It's unstable. Internet download speed it's very slow (1/2 Mbit vs 7/9 with other access point)
I've added a VLAN
VLAN 2 <-- wan port 192.168.1.x
VLAN 3 <-- lan port 5, unbridged, 192.168.100.x with dhcp
VLAN 1 <-- other lan ports & Wifi, 192.168.99.x with BR0
Is there any stable release or this router it's crappy?
40559 soft-bricked the router on update from DD-WRT web interface, soft-bricked from factory firmware as well. Done via direct Ethernet cable from a PC, and two browsers attempted, Chrome and IE11.
30-30-30 resets did not help on any attempt.
Why would that build be in the supported router database on the front page!?
I recovered it using TFTP each time until it finally hard-bricked.
Now the emergency web server doesn't come up and TFTP client can't establish a connection.
The router is in a very rapid boot loop, reboots like every 5 seconds.
Ideas for recovery?
Basically I had a working build from ~2015 that worked adequately (but the web interface responded kind of slow). I was preparing for an installation of a new ISP so I figured I'd check for a firmware update to get the interface to respond quicker... Definitely a regret.
This router had an 80mm fan blowing through modified side panels and Arctic Silver thermal compound under the heatsink from day 1, so my temperatures were in the 30s for the CPU and radio. Kind of sad that a firmware update bricked it when it could have lasted me for years.
Joined: 08 May 2018 Posts: 14210 Location: Texas, USA
Posted: Mon Nov 11, 2019 18:01 Post subject:
I have a better question, if you had a build from 2015: Why did you use the router database for anything and not come to the forum to do your research? Even though it's been updated, the router database is and probably always will be trash.
Anyhow, if you can't use the reset button to reset nvram successfully, then you are likely going to have to do serial recovery. Google DD-WRT serial recovery. Also, that is a 4708, Broadcom ARM. You don't 30-30-30 it. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Posted: Fri Feb 07, 2020 21:33 Post subject: Unsuccessful Trendnet TEW-811DRU AC1200 upgrade
I should have left well enough alone
Tried upgrading my Trendnet TEW-811DRU AC1200
From: v3.0 [Beta] Build 36527 2018-08-09
To: v3.0 [Beta] Build 40559 2019-08-06
Usually the upgrades go great but this is the first time I broke something. The flashing part looked good ending with "successful" but on reboot unable to login or even ping it. (Tried using all ports and wireless)
Tried connecting using multiple cables and computers - no luck. It doesn't show up as wireless network either.
It powers up showing normal LED lights
-power light
-5G light
-2.4G light
-4 ports will light up when plugged/unplugged
Sometimes can see a quick port flash once or twice when pinging it but not the normal port activity flashing LED
I tried using the reset button and powering off/on - no joy
The router does have a USB port and was hoping I could use that to downgrade the firmware
on bootup somehow? but haven't found any info about using the usb port for this.
Joined: 08 May 2018 Posts: 14210 Location: Texas, USA
Posted: Fri Feb 07, 2020 21:48 Post subject:
^^^ Another victim of the router database. Now you have to recover and flash a known good build and then try a newer build to upgrade (or not). I would have to go back to that specific build thread to see if it bricked similar devices or not, but if memory serves, 40559 was a crap build. It should have only soft-bricked and a reset or reboot should've been all that was needed, perhaps, but likely you have gone past the point of know return. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net