can not build firmware properly

[Google Code Exporter]

What steps will reproduce the problem?
1. extract-ng.sh wrt160nl-firmware.bin
2. build-ng.sh /working_directory

What version of the product are you using? On what operating system?
0.76 beta, ubuntu 11.10

Please provide any additional information below.
firmware i used is  DD-WRT v24-sp2 (08/07/10) std (SVN revision 14896) for 
linksys wrt160nl.
the firmware was extracted successfully, i didn't do anything to the firmware 
not even added file or deleted, just built it again, also it was succeed i used 
extract-ng.sh and build-ng.sh
but when i tried to flashed into my router it didn;t go well, my router can not 
boot normally, my LED power kept blinking and i can not  enter the web based 
GUI. does anyone had a same problem? can anyone fix this?? 

Original issue reported on code.google.com by [e-mail] on 12 May 2012 at 8:13

[Google Code Exporter]

I've used the FMK on DD-WRT WRT160N's before, so the firmware should be 
supported. The firmware update may have just gotten corrupted - it happens 
sometimes, even with factory supplied firmware images. If the device's 
bootloader was corrupted or it doesn't provide a fail-safe recovery mode, you 
will need to get lower-level access to the device in order to restore the 
device to a working state, either via a serial port, JTAG, or a flash 
programmer. Unfortunately, there isn't much the FMK can do to help you at this 
point.

Original comment by [e-mail] on 8 Jul 2012 at 11:55

• Changed state: Invalid

[Google Code Exporter]

WRT160N != WRT160NL... very different routers (Atheros vs. Broadcom, Linux vs. 
VXWorks, etc.)

I'm currently having a similar problem with WRT160NLs (not done trying yet, 
though!)

Original comment by [e-mail] on 14 Jul 2012 at 12:13

[Google Code Exporter]

Yes, but A) the WRT160N I have runs Linux (FMk doesn't support non-linux 
firmware) and B) the chipset, in and of itself, should not affect FMK's ability 
to extract the firmware. Besides, he's running it against a DD-WRT firmware, 
which generally uses the same file format, squashfs utilities, firmware 
headers, etc across devices.

Unless there is some other more detailed information that can be provided, iand 
f the *ng scripts were successful with no errors/warnings as the original bug 
report stated, and the router accepted the firmware indicating that the 
firmware headers and checksums were properly modified (which it obviously did), 
I would suspect that it's not an issue with FMK.

But again, if someone can provide more detailed information that indicates 
otherwise, I'll be more than happy to re-open the issue and investigate.

Original comment by [e-mail] on 14 Jul 2012 at 4:34

[Google Code Exporter]

It does seem true that it should work for any WRT160N version that is running 
linux and compatible with DD-WRT images for that device. Like the WRT54G, I'm 
guessing some older versions run linux, some versions don't, and now they have 
the WRT160NL to indicate the linux version. I doubt I will personally get 
around to evaluating this, but Craig might if he has time. I'm currently heavy 
into issuing two major updates for Process Lasso and PECompact, so that's too 
much to keep me busy as is.

Original comment by [e-mail] on 14 Jul 2012 at 11:31