WZR-D1800 De-Bricking Thread

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3, 4, 5, 6  Next
Author Message
Magnetron1.1
DD-WRT User


Joined: 21 Nov 2010
Posts: 278
Location: North America

PostPosted: Wed Jun 26, 2013 17:30    Post subject: Reply with quote
Malachi wrote:

I've done this multiple times. Is there anything else I can do? Is it beyond repair?


While DD-WRT firmware may not work with Omar's router, I think Buffalo firmware could be flashed to it. You mentioned that you tried flashing the Buffalo unencrypted firmware but it did not complete. What where the error messages? What PC operating system did you use and what TFTP apps did you use? I normally use 64 bit Ubuntu version 12.04 Linux to flash firmwwares; however last week I attempted to use tftp2.exe with 64 bit Windows 7 and it would transfer about 75% of the file and then suddenly abort. The CFE running on the router reported fatal I/O errors.
After thinking about it for awhile, I remembered that Windows 7 has an optional TFTP Client component that by default is not installed. After installing it, I used the TFTP client program to successfully flash the unencrypted firmware to one of my Buffalo routers. TFTP when used with no parameters will display help messages.

- Magnetron1.1
Sponsor
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Wed Jun 26, 2013 18:47    Post subject: Reply with quote
Magnetron1.1 wrote:
Malachi wrote:

I've done this multiple times. Is there anything else I can do? Is it beyond repair?


While DD-WRT firmware may not work with Omar's router, I think Buffalo firmware could be flashed to it. You mentioned that you tried flashing the Buffalo unencrypted firmware but it did not complete. What where the error messages? What PC operating system did you use and what TFTP apps did you use? I normally use 64 bit Ubuntu version 12.04 Linux to flash firmwwares; however last week I attempted to use tftp2.exe with 64 bit Windows 7 and it would transfer about 75% of the file and then suddenly abort. The CFE running on the router reported fatal I/O errors.
After thinking about it for awhile, I remembered that Windows 7 has an optional TFTP Client component that by default is not installed. After installing it, I used the TFTP client program to successfully flash the unencrypted firmware to one of my Buffalo routers. TFTP when used with no parameters will display help messages.

- Magnetron1.1

Using windows xp. I've tried the ddwrttobuff 191 you posted. I've used tftp.exe, tftp2.exe, tftpd32 and command line.
I have a Ubuntu 12.10 disc. I can try it using the live cd. If not i have a spare pc I can install it on but I don't know how to do serial or tftp command on Linux.

Here is what it says after trying to upload the revert file you posted:
CFE> flash -noheader : flash1.trx
Reading : : Failed. : I/O error
*** command status = -4

That's using any and all of the tftp processes.

_________________
I am far from a guru, I'm barely a novice.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Wed Jun 26, 2013 19:32    Post subject: Reply with quote
I guess I'll install Ubuntu and try it.
Ubuntu installed. How do I install drivers for the USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter?
Windows installed them automatically. I installed putty already but I keep getting putty fatal error unable to open serial port when I try to open it.

_________________
I am far from a guru, I'm barely a novice.


Last edited by Malachi on Wed Jun 26, 2013 21:52; edited 2 times in total
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Wed Jun 26, 2013 22:37    Post subject: Reply with quote
Still getting the same error on Ubuntu. Terminal error is
Error code 3: transfer cancelled
Sent 33553920 bytes in 14.6 seconds.
Putty error is as before.

Updated putty log from Ubuntu tftp a couple of posts up.

_________________
I am far from a guru, I'm barely a novice.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Thu Jul 04, 2013 18:27    Post subject: Reply with quote
Is this beyond repair?
_________________
I am far from a guru, I'm barely a novice.
Magnetron1.1
DD-WRT User


Joined: 21 Nov 2010
Posts: 278
Location: North America

PostPosted: Sun Jul 07, 2013 3:18    Post subject: Reply with quote
Malachi wrote:
If anyone has the original 1.86 firmware for this router, could you pm me please?
I want to try to flash it through the serial connection. I don't know what else to try.


Won't do any good as the original 1.86 firmware is encrypted. The CFE can't handle encrypted firmwares. I'm currently working on a revised version of the ddwrt2buffalo191 firmware that will be compatible with 32 bit WindowsXP and TFTP.exe software. While my original unencrypted firmware works fine with 64 bit Ubuntu 12.04 linux/TFTP and 64 bit Windows7/TFTP.exe it doesn't seem to work with 32 bit WindowsXP/TFTP.exe.

- Magnetron1.1
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Sun Jul 07, 2013 12:18    Post subject: Reply with quote
Here is the log from a win 7 64bit pc. This is from trying to flash the ddwrt3buff191.bin
Same message when I try to upload the Multi.bin.

Text: 0x87000000 - 0x8704C994 (313748)

DRAM magic offset:00060000 size:00010000
DRAM magic found
Device eth0: hwaddr 12-6F-3F-16-0C-20, ipaddr 192.168.11.1, mask 255.255.255.0
gateway not set, nameserver not set
check_trx: start nflash1.trx
Invalid boot block on disk
check_trx: exit nflash1.trx
fw is broken
blinking led 2
break key pressed!!
CFE> ^C
CFE> nvram erase
*** command status = 0
CFE> flash -noheader : nflash1.trx
Reading :: Failed.: I/O error
*** command status = -4

_________________
I am far from a guru, I'm barely a novice.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Sun Jul 07, 2013 18:45    Post subject: Reply with quote
Here is the log from flashing the Multi.trx

CFE> nvram erase
*** command status = 0
CFE> flash -noheader : flash1.trx
Reading :: Done. 18444288 bytes read
Programming...done. 18444288 bytes written
*** command status = 0
CFE> go
check_trx: start nflash1.trx
check_trx: exit nflash1.trx
Loader:raw Filesys:raw Dev:nflash0.os File: Options:(null)
Loading: .. 1312820 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
CPU revision is: 00019749 (MIPS 74Kc)
Found an ST compatible serial flash with 8 64KB blocks; total size 0MB
found nvram at 50000
something wrong here. do not remap
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
Zone ranges:
Normal [mem 0x00000000-0x07ffefff]
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00000000-0x07ffefff]
Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Linux version 3.8.7 (root@dd-wrt) (gcc version 4.7.3 20121106 (prerelease) (Linaro GCC 4.7-2012.11) ) #162 Mon Apr 15 11:51:57 CEST 2013
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32511
Kernel command line: console=ttyS0,115200 root=1f06 rootfstype=squashfs noinitrd init=/bin/sh
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
__ex_table already sorted, skipping sort
Writing ErrCtl register=80000860
Readback ErrCtl register=80000860
Cache parity protection enabled
Memory: 125652k/131068k available (2953k kernel code, 5416k reserved, 639k data, 304k init, 0k highmem)
NR_IRQS:128
CPU: BCM5300 rev 1 at 600 MHz
bcm947xx_clockevent_set_mode: 1
bcm947xx_clockevent_set_mode: 3
console [ttyS0] enabled
Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: scanning bus 0
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: Fixing up bus 0
pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
Switching to clocksource MIPS
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
Buffalo D1800H init
squashfs: version 3.0 (2006/03/15) Phillip Lougher
msgmni has been set to 245
alg: No test for stdrng (krng)
io scheduler noop registered (default)
HDLC line discipline maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = Cool is a U6_16550A
serial8250: ttyS1 at MMIO 0x0 (irq = Cool is a U6_16550A
brd: module loaded
pflash: found no supported devices
try to find cfe size up to 524288
no filesys. assume nflash devices
bootloader size: 524288
nvram size: 65536
Creating 3 MTD partitions on "bcmsflash":
0x000000000000-0x000000080000 : "cfe"
0x000000070000-0x000000080000 : "nvram"
0x000000070000-0x000000080000 : "nvram_cfe"
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x0000000e0000
nand_read_bbt: bad block at 0x000000140000
nand_read_bbt: bad block at 0x0000018c0000
nand_read_bbt: bad block at 0x0000032a0000
nand_read_bbt: bad block at 0x000003de0000
nand_read_bbt: bad block at 0x0000051c0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =18444288
scan filesys at 140400
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
Broadcom Watchdog Timer: 0.07 initialized.
GACT probability NOT on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1963 buckets, 7852 max)
nf_conntrack_rtsp v0.6.21 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.6.21 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: bic registered
TCP: cubic registered
TCP: westwood registered
TCP: highspeed registered
TCP: hybla registered
TCP: htcp registered
TCP: vegas registered
TCP: veno registered
TCP: scalable registered
TCP: lp registered
TCP: yeah registered
TCP: illinois registered
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
startup nvram driver
found nvram
found cfe nvram
List of all partitions:
1f00 512 mtdblock0 (driver?)
1f01 64 mtdblock1 (driver?)
1f02 64 mtdblock2 (driver?)
1f03 32768 mtdblock3 (driver?)
1f04 97280 mtdblock4 (driver?)
1f05 32768 mtdblock5 (driver?)
1f06 98304 mtdblock6 (driver?)
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,6)
Rebooting in 3 seconds..Please stand by while rebooting the system...

_________________
I am far from a guru, I'm barely a novice.
Magnetron1.1
DD-WRT User


Joined: 21 Nov 2010
Posts: 278
Location: North America

PostPosted: Mon Jul 08, 2013 21:38    Post subject: New Buffalo 191 unencrypted firmware Reply with quote
@Malachi

CMD.exe session of successful flashing of new Buffalo 191 unencrypted f/w using a 32 bit WinXP desktop PC:
C:\WINDOWS\system32>ping 192.168.11.1

Pinging 192.168.11.1 with 32 bytes of data:

Reply from 192.168.11.1: bytes=32 time=1ms TTL=100
Reply from 192.168.11.1: bytes=32 time<1ms TTL=100
Reply from 192.168.11.1: bytes=32 time<1ms TTL=100
Reply from 192.168.11.1: bytes=32 time<1ms TTL=100

Ping statistics for 192.168.11.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

NOTE: Substitute your routers IP address and your firmware location in place of mine in the "tftp" command

C:\WINDOWS\system32>tftp -i 192.168.11.1 put "C:\Download\Buffalo WZR-D1800H\Buf
falo firmware\ddwrt2buff_d1800h191fw\ddwrt2buff_d1800h191fw_m.bin"

Transfer successful: 25620480 bytes in 32 seconds, 800640 bytes/s

C:\WINDOWS\system32>

PuTTY log of successful flashing and booting of new Buffalo 191 unencrypted f/w:
CFE> flash -noheader : nflash1.trx
Reading :: Done. 25620480 bytes read
Programming...done. 25620480 bytes written
*** command status = 0
CFE> go
check_trx: start nflash1.trx
check_trx: exit nflash1.trx
Loader:raw Filesys:raw Dev:nflash0.os File: Options:(null)
Loading: .. 3780742 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
Linux version 2.6.22 (snapshot@snapshot-03) (gcc version 4.2.3) #1 PREEMPT Wed Nov 28 05:09:40 JST 2012
decode_configs:582 cpu options 450a
update_srom_by_nvram: devid=4710
CPU revision is: 00019749
Found an ST compatible serial flash with 8 64KB blocks; total size 0MB
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0 -> 32767
HighMem 32767 -> 32767
early_node_map[1] active PFN ranges
0: 0 -> 32767
Built 1 zonelists. Total pages: 32767
Kernel command line: root=/dev/mtdblock3 console=ttyS0,115200 init=/sbin/preinit
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 512 (order: 9, 2048 bytes)
CPU: BCM5300 rev 1 at 600 MHz
Using 300.000 MHz high precision timer.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 125652k/131068k available (2894k kernel code, 5268k reserved, 593k data, 204k init, 0k highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: Fixing up bus 0
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
HDLC line discipline: version $Revision: 1.1.1.1 $, maxframe=4096
N_HDLC line discipline registered.
mel_initsw initialized.
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = Cool is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = Cool is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE compression module registered
NET: Registered protocol family 24
drivers/mtd/mtdchar.c(842): alloc reserved-buffer addr=87e00000 size=131072
pflash: found no supported devices
Boot partition size = 262144(0x40000)
Creating 2 MTD partitions on "sflash":
0x00000000-0x00040000 : "boot"
0x00070000-0x00080000 : "nvram"
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
nflash: scanning bad blocks...
nflash: bad block found at 11 [00160000]
nflash: bad block found at 130 [01040000]
nflash: bad block found at 401 [03220000]
nflash: bad block found at 991 [07BE0000]
nflash: scanning bad blocks done
bcm_nflash: ecc support 1
lookup_nflash_rootfs_offset: offset = 0x0
nflash: squash filesystem with lzma found at block 12
Creating 3 MTD partitions on "nflash":
0x00000000-0x02000000 : "kernel"
0x0017fa3c-0x02000000 : "rootfs"
0x00000000-0x02000000 : "linux"
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Creating 1 MTD partitions on "brcmnand":
0x07700000-0x07f00000 : "user_property_raw"
u32 classifier
nf_conntrack version 0.5.0 (1023 buckets, 8184 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
...
Please press Enter to activate this console.
...
BusyBox v1.00 (2012.11.27-20:15+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

#

End of Logs


- Magnetron1.1



ddwrt2buff_d1800h191fw_m.bin
 Description:
md5sum = 6392c15a26687621d644bc10c9790451

Download
 Filename:  ddwrt2buff_d1800h191fw_m.bin
 Filesize:  24.43 MB
 Downloaded:  1286 Time(s)

Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Mon Jul 08, 2013 21:50    Post subject: Reply with quote
I'll try it. Thanks.

Edit: It's ALIVE! Thanks Magnetron 1.1. Should be 2.0 now.
What was the problem? Something an idiot like me could grasp? Lol

My putty log after successful flash looks a little different than yours but I'm in the router GUI. Is it safe to flash the community build? Or is there something defective with this unit?
This buffalo GUI is hideous. Lol

_________________
I am far from a guru, I'm barely a novice.
Magnetron1.1
DD-WRT User


Joined: 21 Nov 2010
Posts: 278
Location: North America

PostPosted: Mon Jul 08, 2013 23:51    Post subject: Reply with quote
Malachi wrote:
I'll try it. Thanks.

Edit: It's ALIVE! Thanks Magnetron 1.1. Should be 2.0 now.
What was the problem? Something an idiot like me could grasp? Lol

My putty log after successful flash looks a little different than yours but I'm in the router GUI. Is it safe to flash the community build? Or is there something defective with this unit?
This buffalo GUI is hideous. Lol


I reduced the firmware file size to correspond to the file length field specified in the f/w header by removing 7 MB of useless hex FF's which can cause problems with some combinations of software and hardware.

I omitted about 90% of the PuTTY log information from my post.

Based on your previous PuTTY logs, I would use the Buffalo WebGUI to flash build 21676 WZR-D1800H_MULTI.bin. (Remember ... Buffalo f/w is expecting encrypted firmwares when upgrading.) I give it a 50/50 chance of working. Yes, I suspect the NAND flash has bad blocks in critical areas for the DD-WRT firmwares. Even if DD-WRT doesn't work, you can always restore the Buffalo factory firmware.

- Magnetron1.1
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Tue Jul 09, 2013 0:50    Post subject: Reply with quote
Thanks. I will try it. So the NAND could be defective. Is that something that is caused by a bad flash?
I did read in another thread that you say not to use build 21676 as it bricks the router. I know I can recover it but did something change from your other recommendation here
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=172272&postdays=0&postorder=asc&start=6

_________________
I am far from a guru, I'm barely a novice.
Magnetron1.1
DD-WRT User


Joined: 21 Nov 2010
Posts: 278
Location: North America

PostPosted: Tue Jul 09, 2013 3:42    Post subject: Reply with quote
Malachi wrote:
Thanks. I will try it. So the NAND could be defective. Is that something that is caused by a bad flash?
I did read in another thread that you say not to use build 21676 as it bricks the router. I know I can recover it but did something change from your other recommendation here
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=172272&postdays=0&postorder=asc&start=6


I suppose that a critical sector could have failed during a flash event but odds are it was bad before flashing.

I still don't recommend upgrading to build 21676 based on my experience especially for users that don't have a serial cable. After randomly selecting 4 of my 6 routers for upgrading from build 21286, build 21676 bricked the first 3 routers. Router #4 successfully flashed and booted. If I had continued, routers #5 and #6 also would have been bricked. After comparing the serial logs of the first four routers, I now know what to look for.

After examining your PuTTY log of the router attempting to boot build 21286, I saw this:
Creating 3 MTD partitions on "bcmsflash":
0x000000000000-0x000000080000 : "cfe"
0x000000070000-0x000000080000 : "nvram" <= Build 21676 must see "nvram" and "nvram_cfe" partitions occupying the same addr space
0x000000070000-0x000000080000 : "nvram_cfe" <= Same addr space as "nvram". Build 21676 has a fighting chance of working.
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64

Currently, all 6 of my Buffalo routers are running build 21676; however I'm still working on the upgrade procedure.

- Magnetron1.1
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Tue Jul 09, 2013 20:52    Post subject: Reply with quote
Any other build I try to put on it results in the same kernel panic as before. The only thing that works is the modified factory fw you gave me Megatron1.1
I wonder if I will ever be able to even upgrade the official buffalo releases, assuming there will be any.

_________________
I am far from a guru, I'm barely a novice.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Sun Jul 14, 2013 20:51    Post subject: Reply with quote
I was able with magnetron's help, to get stock firmware back on it. You were able to use draytek to flash dd-wrt onto it?
_________________
I am far from a guru, I'm barely a novice.
Goto page Previous  1, 2, 3, 4, 5, 6  Next Display posts from previous:    Page 3 of 6
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum