Posted: Sun Oct 26, 2014 21:42 Post subject: Bricked r7000 by oc (1400MHz) [SOLVED]
Hello everyone, I'm a fairly new user of dd-wrt and I need some help/advice.
Today I bricked my R7000 when setting the clock to 1400MHz using dd-wrt 25143 (BS) in the web-gui.
Is it "safe" to oc from the web-gui? 1200MHz seemed to work fine.
The situation at the moment is that the power led is solid red/orange, I've tried to reset the router with the reset button without results. My LAN is working but not wifi or WAN.
Telnet and ssh times out.
Is there anything else I can do except to get an serial cable?
image.jpg
Description:
Filesize:
32.1 KB
Viewed:
19170 Time(s)
Last edited by niXta on Thu Oct 30, 2014 0:01; edited 2 times in total
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Mon Oct 27, 2014 18:19 Post subject:
overclocking is never safe. its not stable on all devices in the same way. its like if you tune your care and break your engine if it gets to much. so far i was able to recover the most devices with a serial cable since bootloader almost comes up, but linux will crash later. and with the cfe console you can reset the nvram (nvram erase command) _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
overclocking is never safe. its not stable on all devices in the same way. its like if you tune your care and break your engine if it gets to much. so far i was able to recover the most devices with a serial cable since bootloader almost comes up, but linux will crash later. and with the cfe console you can reset the nvram (nvram erase command)
Thanks _________________ My Routers - NETGEAR R7000
Firmware: DD-WRT v3.0-r40270M kongac (07/11/19)
Kernel: Linux 4.4.185 #670 SMP Thu Jul 11 02:19:39 CEST 2019 armv7l
http://www.desipro.de/ddwrt/K3-AC-Arm/ ---------------------------------------------------------------- - TP-LINK TL-WR1043ND V2
Firmware version: LEDE Reboot 17.01.4 (18/10/17)
Kernel: Linux version 4.13.3
https://downloads.lede-project.org/releases/ ---------------------------------------------------------------- http://www.ncsacademy.com/default.cfm?ref=28555
overclocking is never safe. its not stable on all devices in the same way. its like if you tune your care and break your engine if it gets to much. so far i was able to recover the most devices with a serial cable since bootloader almost comes up, but linux will crash later. and with the cfe console you can reset the nvram (nvram erase command)
True, I was just wondering if it was as safe to OC via web-gui as using the terminal command?
Would TFTP over LAN work in this case or do I need to get a serial cable right away?
Posted: Wed Oct 29, 2014 23:30 Post subject: Great success!
haggismn wrote:
A serial cable is required. Something like this will work perfectly.
Got exactly that one from a local shop at 10x $.
Everything worked out great!
Just a note to others; open your serial program with admin privileges (if using Windows). And if all led's lights up, switch TX and RX (my manual was incorrect).
Continuing to rock my (crappy chip) R7000 with dd-wrt@1200mhz!
Joined: 24 Oct 2009 Posts: 319 Location: Buenos Aires-Argentina, End of World and new Pope's home.
Posted: Thu Oct 30, 2014 0:59 Post subject:
Great! Congrats!
Mine is lucky it works @ 1400 since months. _________________ R7000 testing XVortex/Merlin's firm as AP @ home, VOIP, wifi printer, Roku 3 & 8 clients, Guest wifi, 2 wifi cameras, USB storage. Great firm. No more 1400 oveclocked, no need.
RT-N16 on VicTek's Raf Beta 9014-v1.3d. repeater @ Condominium pool side, a lot of clients messing arround.
wrt600n on wrt610n firm 16214 @ warehouse for 22 colleagues as wifi client @ 2.4 Ghz and 5 Ghz just for me.
wrt54gl on Eko's @ warehose as repeater for 22 coleagues as wifi client
wrt350n oldie 2007, 5 years bricked, recovered from dead & modded with antennas and new agn radio now incredible "NA mixed" on Brainslayer's , repeater at my garage, modding as hobby (picture)
All at service.
Kong said: Yeah that stupid 30/30/30. I already said it multiple times on newer units build in the last 2 years this is not the way to do it
Last edited by mito on Thu Oct 30, 2014 11:54; edited 1 time in total
I have no issues running mine at 1400/800 from day one.
Can't complain
Sweet, you got a better chip than I got!
I've overclocked a lot of stuff through the years so why let my router off easy
I'm not really in the need of OC atm, but I will probably run a VPN-server in a few months so I wanted to know how high it goes if I need it.
Still, I would advise against anyone trying 1400MHz without some knowledge and a serial cable ready.
I haven't seen anyone get bricked @ 1200MHz though, so I guess that should be the advice to eager newcomers.
Thanks again for the help and of course for dd-wrt! _________________ _______________________
Netgear R7000
@niXta, since you posted a nice pic of your router with the top cover openend. Did you manage to open it without breaking anything?
I tried to remove my top cover and gave up because the side where the antennae are connected was somehow stuck.
@niXta, since you posted a nice pic of your router with the top cover openend. Did you manage to open it without breaking anything?
I tried to remove my top cover and gave up because the side where the antennae are connected was somehow stuck.
Yes, no need to break anything.
I used a very small screwdriver to lift the locking clips on the side with antennas. The screwdriver was inserted through a vent hole in the side. The middle clip can be lifted from the back through the antenna cut out.
I also recommend painting the plastic led "transporters" on the inside to get a nice weak dimmed lights effect. _________________ _______________________
Netgear R7000