my serial number doesnt work any idea or luck for yourself?
Support and warranty will be with the US in this case. Our website will only allow downloads from an EU serial number. Check on the US site:
http://www.buffalotech.com
Regards,
David
Buffalo Technology Helpdesk
Quote:
so any one with EU serial number can you please check and tell
How can I flash my DDWRT back to stock FW?
I downloaded the Professional firmware (dd-wrt based) 48.68 M. Following the instruction, flash to wzr1750dhp-pro-v23sp2-23709a-eu, then flash to wzr1750dhp-userfriendly-2.24-eu, then it bricks. Then I need to use TTL to recover to other DDWRT version
As I know somebody can go back to 2.22 eu from 23709a. Can you upload the 2.22 eu FW? Otherwise any alternative solution?
Thank you
my serial number doesnt work any idea or luck for yourself?
Support and warranty will be with the US in this case. Our website will only allow downloads from an EU serial number. Check on the US site:
http://www.buffalotech.com
Regards,
David
Buffalo Technology Helpdesk
Quote:
so any one with EU serial number can you please check and tell
How can I flash my DDWRT back to stock FW?
I downloaded the Professional firmware (dd-wrt based) 48.68 M. Following the instruction, flash to wzr1750dhp-pro-v23sp2-23709a-eu, then flash to wzr1750dhp-userfriendly-2.24-eu, then it bricks. Then I need to use TTL to recover to other DDWRT version
As I know somebody can go back to 2.22 eu from 23709a. Can you upload the 2.22 eu FW? Otherwise any alternative solution?
Thank you
that depends, do you have terminal cable access, otherwise you need to scan the forums to get your luck.
Or you can try here, which worked for me,
And can you upload the pro-firmware somewhere and post us the link, thanks.
Posted: Sat Mar 07, 2015 0:05 Post subject: Fixing dead Buffalo WZR-1750DHP
Hello Guys,
I've been using my router for long time without issues. I was using one of the latest beta builds from Jan or Feb, I don´t remember exactly what was.
I was changing some QoS parameters and the router suddenly dies.
I´ve experience with a dead buffalo DHP-D of a friend and using the serial cable we were be able to fix it.
I don't really have enough experience to determine what's wrong, however I've erased the nvram and flashed again but I'm having the same boot loop issue.
After that the router seems to boot in normal way and this caught my attention:
Creating 5 MTD partitions on "bcmsflash":
0x000000000000-0x000000100000 : "boot"
0x000000000000-0x0000000f0000 : "linux"
0x000000100000-0x000000100000 : "rootfs"
mtd: partition "rootfs" is out of reach -- disabled
0x0000000f0000-0x000000100000 : "nvram_cfe"
0x0000000e0000-0x0000000f0000 : "nvram"
and later
Creating 1 MTD partitions on "brcmnand":
0x000000000000-0x000008000000 : "ddwrt"
end_request: I/O error, dev mtdblock2, sector 0
SQUASHFS error: sb_bread failed reading block 0x0
VFS: Cannot open root device "1f02" or unknown-block(31,2): error -19
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 960 mtdblock1 (driver?)
1f03 64 mtdblock3 (driver?)
1f04 64 mtdblock4 (driver?)
1f05 131072 mtdblock5 (driver?)
1f06 131072 mtdblock6 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
CPU1: stopping
and later a message which says:
Rebooting in 10 seconds..
If any of you guys could help me I´ll appreciate a lot, I don´t want to buy another router.
Posted: Sat Mar 07, 2015 7:00 Post subject: Re: Fixing dead Buffalo WZR-1750DHP
nein wrote:
Hello Guys,
I've been using my router for long time without issues. I was using one of the latest beta builds from Jan or Feb, I don´t remember exactly what was.
I was changing some QoS parameters and the router suddenly dies.
I´ve experience with a dead buffalo DHP-D of a friend and using the serial cable we were be able to fix it.
I don't really have enough experience to determine what's wrong, however I've erased the nvram and flashed again but I'm having the same boot loop issue.
After that the router seems to boot in normal way and this caught my attention:
Creating 5 MTD partitions on "bcmsflash":
0x000000000000-0x000000100000 : "boot"
0x000000000000-0x0000000f0000 : "linux"
0x000000100000-0x000000100000 : "rootfs"
mtd: partition "rootfs" is out of reach -- disabled
0x0000000f0000-0x000000100000 : "nvram_cfe"
0x0000000e0000-0x0000000f0000 : "nvram"
and later
Creating 1 MTD partitions on "brcmnand":
0x000000000000-0x000008000000 : "ddwrt"
end_request: I/O error, dev mtdblock2, sector 0
SQUASHFS error: sb_bread failed reading block 0x0
VFS: Cannot open root device "1f02" or unknown-block(31,2): error -19
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 960 mtdblock1 (driver?)
1f03 64 mtdblock3 (driver?)
1f04 64 mtdblock4 (driver?)
1f05 131072 mtdblock5 (driver?)
1f06 131072 mtdblock6 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
CPU1: stopping
and later a message which says:
Rebooting in 10 seconds..
If any of you guys could help me I´ll appreciate a lot, I don´t want to buy another router.
Attached the full verbose.
Thanks!!!!!
buddy i had this issue long time ago, long really long, and how i rebuild i don't know but i think thru serial i kept pushing the build in and some how it booted.
i am attching cfe bin of my router, but its wzr-dhp1750.
Posted: Sun Mar 08, 2015 2:22 Post subject: Damaged CFE?
Thank you, so it seems you have my same router.
So maybe the CFE is damaged?
Anyone could help me with the steps to flash again the CFE.bin backup?
Edit: I found this:
flash -noheader : cfe.bin flash1.boot
However I´ve my doubts,
flash1.boot ST Compatible Serial flash offset 00000000 size 256KB
flash1.trx ST Compatible Serial flash offset 00040000 size 704KB
flash1.nvram ST Compatible Serial flash offset 000F0000 size 64KB
The flash1.boot is 256KB and the cfb.bin is 1024KB.
Any ideas?
Last edited by nein on Wed Mar 11, 2015 1:36; edited 1 time in total
Posted: Thu Mar 12, 2015 15:26 Post subject: Steps
drderr wrote:
please post the steps you made and commands you did for cfe reflashing. thanks
edit: I saw you reedit the post above. thanks
Anyway, I did this:
The modem was in an infinite boot loop no matter what after doing regular changes in the webgui.
I opened and using the USB-Serial cable I managed to push several builds without luck (I was able to fix a router from a friend just pushing again the Firmware and cleaning the nvram)
Imranjamadar suggested that the CFE was corrupted and in a previous post he posted one from his 1750DHP, his CFE.bin size is 1024KB, however checking in my router the sum of all was 1024KB, so I decided to flash the flash1.boot hoping to overwrite the flash1.trx and flash1.nvram.
flash1.boot ST Compatible Serial flash offset 00000000 size 256KB
flash1.trx ST Compatible Serial flash offset 00040000 size 704KB
flash1.nvram ST Compatible Serial flash offset 000F0000 size 64KB
This was the command:
flash -noheader : cfe.bin flash1.boot
After doing that without turn off I pushed again a DD-WRT build and cleaned the nvram.
I've restarted the modem and everything worked like a charm.
FYI: the router MAC changed to the Imranjamadar's, but it doesn't matter, it's alive again.
Posted: Fri Mar 13, 2015 11:43 Post subject: Re: Steps
nein wrote:
drderr wrote:
please post the steps you made and commands you did for cfe reflashing. thanks
edit: I saw you reedit the post above. thanks
Anyway, I did this:
The modem was in an infinite boot loop no matter what after doing regular changes in the webgui.
I opened and using the USB-Serial cable I managed to push several builds without luck (I was able to fix a router from a friend just pushing again the Firmware and cleaning the nvram)
Imranjamadar suggested that the CFE was corrupted and in a previous post he posted one from his 1750DHP, his CFE.bin size is 1024KB, however checking in my router the sum of all was 1024KB, so I decided to flash the flash1.boot hoping to overwrite the flash1.trx and flash1.nvram.
flash1.boot ST Compatible Serial flash offset 00000000 size 256KB
flash1.trx ST Compatible Serial flash offset 00040000 size 704KB
flash1.nvram ST Compatible Serial flash offset 000F0000 size 64KB
This was the command:
flash -noheader : cfe.bin flash1.boot
After doing that without turn off I pushed again a DD-WRT build and cleaned the nvram.
I've restarted the modem and everything worked like a charm.
FYI: the router MAC changed to the Imranjamadar's, but it doesn't matter, it's alive again.
Congrats to all those who achieved a dead router alive again.
Try changing your mac address to yours again, if possible or ask buffalo.
If anyone is interested...
I was using BS 23919 with optware installed and had python, sickrage (sickbeard fork), git, and several other utils installed, all operating mostly ok (git was messed up and wget had no ssl and wouldn't install). I had been wanting to upgrade for quite a while to a newer build, but was unable to because ipkg is broken (there's a ticket open about it) and every guide I had found used ipkg to install opkg. Finally, I found the entware-arm project, which appears to be a very updated version of optware (which looks like it might be going obsolete). What I did was...
Formatted my USB with a 512MB ext4 partition labeled opt, a 128MB Linux-swap partition, and another ext4 partition labeled data.
Setup my USB - Goto Services, USB, and enable core usb support, usb storage support, and automatic drive mount, then click apply. After this I had jffs2 mounted to /jffs, my usb opt partition mounted to /opt, my swap partition mounted to swap, and my data partition mounted to /mnt/sda3
Telnet into the router so you have command line access, and run...
Code:
cd /jffs
mkdir -m 777 scripts
cd /opt
wget -O http://qnapware.zyxmon.org/binaries-armv7/installer/entware.arm-setup.sh
chmod +x entware.arm-setup.sh
sh entware.arm-setup.sh
Select the space you want to install Entware.arm to (in my case 3 which was my opt partition) and let it run.
Once that was done I had Entware fully running and opkg installed and working perfectly, and simply needed to start installing packages I needed. For me it works just like Optware did on the older 23919 firmware, but small issues I had with git and wget are gone. Hope this helps someone who was also trying to get opkg running. Also, once Entware is installed you can even install Debian-Wheezy if you'd like.
