[Malachi]

I have backed up the cfe using the backup/cfe.bin from the browser.
I then compare it to the backup from the cfe I get from jtag and it doesn't match.
I've also backed it up multiple times using jtag and they never match.
I've tried using -backup:cfe /cable:dlc5 /byte_mode and with out byte mode. Always different.

The router was acting weird. It woukd get nonresponsive. Only 1 lan port would work.
I could ping it and get responses then after a while no more ping responses. It would need a reboot.
I erase the nvram using serial and re flashed both dd-wrt and stock. It wou,d still become unresponsive.
Any clues?

[barryware]

time to invest in a buffered cable (wiggler)

[Malachi]

The one I have can do both. So use buffered? Ok.
It becomes unresponsive anytime a change is made. Do you think erasing everything and flashing back would help?

[barryware]

do not erase cfe or whole flash.. so far, you can not get a good backup (backup twice and compare). What makes you think you will get a good write?

there is nothing wrong with the cfe.. you have to try to mess up a cfe.

what is the history of the router? are you using the right power supply?

[Malachi]

Three errors only using buffered at an erea called "flash device write area"
I'm using a 4A power supply from my netgear r6300.
As to history..... Bought it like this to experiment.
Bored.

Edit: this is weird. Backed it up a third time. Backup #1 doesn't match the backup from the web GUI backup. But #2 backup from jtag matches.
Going to try a third time. Third one matches.

You don't think erasing wholeflash and re-flashing the cfe will help?
What could be wrong? I'm used to cars where there are moving parts that can break.
Nothing is mechanical in here.
What would make it be unresponsive after a change of any settings?
I don't think it's overheating. I can touch everything while its running and it doesn't feel hot.

[barryware]

what could be wrong?? Could be that the router is fubar.. You bought it bricked. Not all bricked routers bricked because of a bad flash.

So... have at it. it is already broke, you can't fuck it up any more.

I would test your writes by writing nvram, backing up and comparing..

as said, to fubar a cfe, you gotta try and there were no cfe "updates" for the n16 like there was for the n66.

live long and prosper.. may the force be with you.

good luck.. have a nice Easter..

[Malachi]

Thanks barryware. Happy Easter to you.
Already erased wholeflash. Now flashing the cfe. Btw it wasn't totally bricked. Just didn't work right.
Fun anyway. Lol

I don't know how to write any nvram values to it. Never copied that step before.

[Malachi]

Flashed the cfe. Still the same problem. Coud it be the cfe it self? Should I try one from the cfe collection? Or give up?

[Malachi]

Different cfe, same outcome. Junk.