Hi guys, i've found this topic while looking for a fix to a hudge problem that i'm experiencing since yesterday.
It all started while i was trying to overclock my r6300v2 after i put a custom 12mm FAN on the heathsink (wich have dropped my cpu temps from 71c to 45c)... during my test i tried to set a clock speed of 1600, and after that the router seems to have died.
I've tried at least 100 times to recover using ttl as i have always done on other routers, but every time the serial console freezes a couple of second after loading.
This is the only output i get every time:
Code:
Digital core power voltage set to 0.9375V
Decompressing...done
I would really appreciate any kind of help because the router is out of warranty and it was my primary unit to manage my home network...
The unit was running Kong latest build.
I have experience with smd soldering and i'm ready to try every crazy idea
Hi guys, i've found this topic while looking for a fix to a hudge problem that i'm experiencing since yesterday.
It all started while i was trying to overclock my r6300v2 after i put a custom 12mm FAN on the heathsink (wich have dropped my cpu temps from 71c to 45c)... during my test i tried to set a clock speed of 1600, and after that the router seems to have died.
I've tried at least 100 times to recover using ttl as i have always done on other routers, but every time the serial console freezes a couple of second after loading.
This is the only output i get every time:
Code:
Digital core power voltage set to 0.9375V
Decompressing...done
I would really appreciate any kind of help because the router is out of warranty and it was my primary unit to manage my home network...
The unit was running Kong latest build.
I have experience with smd soldering and i'm ready to try every crazy idea
Please help
Stop the boot sequence using CTRL+C to enter CFE (I usually hold down both keys as soon as I've powered on the router and the boot sequence stops as soon as it gets to correct section where it stops).
Then follow these steps (which I have just done on my own router that I bricked on purpose by changing the clock speed to 1600 too).
CFE> nvram get clkfreq
1600,533
*** command status = 0
CFE> nvram set clkfreq=800,533
*** command status = 0
CFE> nvram commit
*** command status = 0
CFE> nvram get clkfreq
800,533
*** command status = 0
CFE> reboot
Credit goes to lots of other previous posts discussing similar problems. The difference being that I've recreated the problem as I was interested in it.
Hi guys, i've found this topic while looking for a fix to a hudge problem that i'm experiencing since yesterday.
It all started while i was trying to overclock my r6300v2 after i put a custom 12mm FAN on the heathsink (wich have dropped my cpu temps from 71c to 45c)... during my test i tried to set a clock speed of 1600, and after that the router seems to have died.
I've tried at least 100 times to recover using ttl as i have always done on other routers, but every time the serial console freezes a couple of second after loading.
This is the only output i get every time:
Code:
Digital core power voltage set to 0.9375V
Decompressing...done
I would really appreciate any kind of help because the router is out of warranty and it was my primary unit to manage my home network...
The unit was running Kong latest build.
I have experience with smd soldering and i'm ready to try every crazy idea
Please help
Get a new router. _________________ I am far from a guru, I'm barely a novice.
The tftp is on 192.168.1.2 - sorry for not providing this detail earlier.
I will try again otherwise I will explore recovery via serial.
Thank you again.
Hi... I'm getting similar problem on r6300v2, it keep rebooting after flashing factory-to-dd-wrt.chk
1. Router is ping-able for few seconds in every reboot with TTL=100
2. Not able to tftp 192.168.1.1 to flash the rom, using Linux tftp program with 1 second re-transmission parameter for 600 seconds, still no luck
3. Setup a TFTP server @ 192.168.1.2 with vmlinuz, but no log showing the router is trying to fetch this file
Any suggestion to debrick the device without opening the router case please?
Troubleshooting without a serial connection is difficult. However, the first thing that I would do is verify the functionality of the TFTP server, say, by pulling the vmlinuz file from another client.
The tftp is on 192.168.1.2 - sorry for not providing this detail earlier.
I will try again otherwise I will explore recovery via serial.
Thank you again.
Hi... I'm getting similar problem on r6300v2, it keep rebooting after flashing factory-to-dd-wrt.chk
1. Router is ping-able for few seconds in every reboot with TTL=100
2. Not able to tftp 192.168.1.1 to flash the rom, using Linux tftp program with 1 second re-transmission parameter for 600 seconds, still no luck
3. Setup a TFTP server @ 192.168.1.2 with vmlinuz, but no log showing the router is trying to fetch this file
Any suggestion to debrick the device without opening the router case please?
Troubleshooting without a serial connection is difficult. However, the first thing that I would do is verify the functionality of the TFTP server, say, by pulling the vmlinuz file from another client.
Thanks for pointing out, I disabled some firewall, but yet it still not work and no log showing it is trying to connect to the tftp server. Is the router IP address will be 192.168.1.1?
tftp successfully from another PC:
c:\Users\User\Desktop>tftp -i 192.168.1.2 get vmlinuz
Transfer successful: 8539654 bytes in 7 second(s), 1219950 bytes/s
The tftp is on 192.168.1.2 - sorry for not providing this detail earlier.
I will try again otherwise I will explore recovery via serial.
Thank you again.
Hi... I'm getting similar problem on r6300v2, it keep rebooting after flashing factory-to-dd-wrt.chk
1. Router is ping-able for few seconds in every reboot with TTL=100
2. Not able to tftp 192.168.1.1 to flash the rom, using Linux tftp program with 1 second re-transmission parameter for 600 seconds, still no luck
3. Setup a TFTP server @ 192.168.1.2 with vmlinuz, but no log showing the router is trying to fetch this file
Any suggestion to debrick the device without opening the router case please?
Troubleshooting without a serial connection is difficult. However, the first thing that I would do is verify the functionality of the TFTP server, say, by pulling the vmlinuz file from another client.
Thanks for pointing out, I disabled some firewall, but yet it still not work and no log showing it is trying to connect to the tftp server. Is the router IP address will be 192.168.1.1?
tftp successfully from another PC:
c:\Users\User\Desktop>tftp -i 192.168.1.2 get vmlinuz
Transfer successful: 8539654 bytes in 7 second(s), 1219950 bytes/s
Good to see that you have verified the TFTP server.
Correct, the address of the router should be 192.168.1.1. Since you get a ping response confirms the router has this address.
When I last played with the router to intentionally brick it so that I could look at recovery options the router did not always wait for the vmlinuz file. I will need to check some of my screenshots of the console session when I was playing with the router to see if there is a way to force the router to wait for the vmlinuz file. I will post back later today or tomorrow.
