Goflex Net fail -need help to unbrick

Hello,

i have an almost new Goflex Net device, that i wanted to run debian. After trying different solutions (installing debian and rescue), i have problem with my device.

I cannot install a new uboot, and the only way i can access it is through the serial port with uart boot. I tried some of the suggestions in the forum, but i am stuck with it.
It seems the first nand block is bad. I want to ask the experts, what to do to get it running, if somebody could help me with unbricking. I hope there is some light chance to use it :)

I can boot it by uart to the dns-320 image on the usb, but i cannot install uboot. The script ends with verification failed. I tried writing with nandwrite (found in this forum that somebody managed to repair it with the same symptoms) with no success.

I cannot get further. Here is my log:

##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.

root@debian-kirkwood-wide:/tmp# /usr/sbin/flash_erase /dev/mtd0 0 5
Erase Total 5 Un[ 748.998066] nand_erase_nand: attempt to erase a bad block at page 0x00000000
its
Performing Flash Erase of length 131072 at offset 0x0
MTD Erase failure: Input/output error
root@debian-kirkwood-wide:/tmp# /usr/sbin/nandwrite /dev/mtd0 uboot.mtd0.kwb
Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
td0t@debian-kirkwood-wide:/tmp# nanddump -bnof /tmp/uBoot.dump -l 0x80000 /dev/m
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
root@debian-kirkwood-wide:/tmp# diff -s uboot.mtd0.kwb uBoot.dump
Binary files uboot.mtd0.kwb and uBoot.dump differ
root@debian-kirkwood-wide:/tmp#

Any help is much appreciated.

daveeeee,

The saved image and what in NAND differs because looks like you've dumped it starting at block 0, which is your bad block. Try:

nanddump -bnof /tmp/uBoot.dump -l 0x80000 -s 0x20000 /dev/mtd0

Do the diff again afterward, if the saved image uboot.mtd0.kwb is identical with uBoot.dump then you can flash the uBoot env.

Situation is the same:

root@debian-kirkwood-wide:/tmp# nanddump -bnof /tmp/uBoot.dump -l 0x80000 -s 0x20000 /dev/mtd0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00020000 and ending at 0x000a0000...
root@debian-kirkwood-wide:/tmp# diff -s uboot.mtd0.kwb uBoot.dump
Binary files uboot.mtd0.kwb and uBoot.dump differ

:(

Did you try flash_erase and nandwrite again before nanddump?

Yes, i did. Thank you for helping,

i finally succeeded to write uboot by interrupting boot and using tftpboot, nand erase and nand write.e, according this topic.
It worked without problem, so my device is alive :)

it is a little strange, that i tried this before, but some errors were reported. But now, it fixed my problem.