just an FYI, xVortex says he corrected the corruption causing firmware.
If you want to go back to NG it should work and allow you to revert like normal. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
just an FYI, xVortex says he corrected the corruption causing firmware.
If you want to go back to NG it should work and allow you to revert like normal.
I waited on the NG firmware for a long time until he posted it was fixed. I wonder if it came from the original 380.70
I was testing NG for the QoS but after about 10 days of testing I concluded that Kongs QoS works better then Trend Micros QoS.
It seems like the problem reared its head back. After flashing xVortex, reverting back to oem is not a problem. The issue arises after flashing dd-wrt.
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
Be careful and change the name "stock-cfe.bin" to the one in the first link.
so i am on the same boat after VORTEX. i'm really new to this kind of staff and i really don't know what to do now.
i can really use any help, please.
how can i restore the cfe?
Everything you need is in this thread here that you found.. Then jumped to the end to creat your own post as if you were the first this has happened to?
Did you at least download & read the provided information contained in the post you quoted?
What is said about this over at the xVortex forums? This is there bag of crap.. not dd-wrt's
It's been more than a year now & they still provide this firmware? Not even with any disclosure/warning? _________________ Location 1
R6300V2- DD-WRT v3.0-r39345M kongac (04-03-19) Gateway
WNDR3400v1 DD-WRT.v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R6300V2- DD-WRT v3.0-r39345M kongac (04/03/19) Gateway
R6300V2- DD-WRT v3.0-r39345M kongac (04/03/19) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
2 devices: SXT 5 ac (mipsbe) RB 6.46.4 (2/21/20) PTP Bridge (0.8km/0.5mi)tx/rx866.6Mbps-1GbpsLAN
Thank You BrainSlayer & <Kong> for ALL that you do & have done, also to "most" everyone here that shares their knowledge
No the stock firmware will not fix the damage to the cfe. You will have to restore an undamaged copy. Luckily the cfe on the R7000 is generic. One was posted a while back that can be used, but first I highly recommend that you read all the posts I have made on this issue.
You probably had xwrt-vortex 384.x on your router. That firmware seriously screwed up the cfe on the router. If you have a copy of that, you need to restore it. I had the same problem and just fixed it yesterday. I had corrupted boardid, mac, sn and had to use the burn command after going back to stock. Came back to dd-wrt and had the same issue as you. Configure the router, works great, reboot and it resets. If you have a serial ttl cable and can look at the output right after boot you will likely see something like this after all the x's and +'s.
A year later and sadly we're still getting flubbed up with the this crap. I thought I wanted to try something with an updated UI... look where it got me.
OK, at least now I know what happened - THANKS greatly for getting to the bottom of this.
Is this still a problem?
I had 384.14_2 on the router and DD-WRT config wasn't saving.
I kinda think you answered your own question. I never got around to fixing my CFE. I'm reasonably happy with fresh tomato - but yes, I do still think about getting back to dd-wrt.
