bdrestore fails: how to recover board config for dir-300?

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3, 4  Next
Author Message
jb86
DD-WRT Novice


Joined: 10 Nov 2008
Posts: 6

PostPosted: Mon Dec 15, 2008 20:33    Post subject: Reply with quote
oh if you can speak chinese I think I can help you
I rebuild redboot and disable the last 0x10000 limit
Sponsor
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Mon Jan 05, 2009 21:21    Post subject: Reply with quote
Happy new yrs! Hope everyone had good holidays. Has anyone been able to come up with a detailed success story for recovering using the provided .bin's above?
Domino_55
DD-WRT User


Joined: 15 Sep 2008
Posts: 88

PostPosted: Wed Jan 21, 2009 8:57    Post subject: Reply with quote
Is this method is usable for the original firmware restoration with original MAC address and with working WPA and others?
lider404
DD-WRT Novice


Joined: 08 Jun 2008
Posts: 27

PostPosted: Sun Jan 25, 2009 19:08    Post subject: Reply with quote
Not for me... I tryied to restore to orginal after killing board config, but router loads only in dd-wrt, and i can go back to the orginal ONLY after flashing router to dd-wrt. So WPA doesn't work.
P.S. Soory for english.
systm
DD-WRT Novice


Joined: 01 Oct 2008
Posts: 40
Location: USA

PostPosted: Thu Jan 29, 2009 21:21    Post subject: Reply with quote
hmm so i did all that- and back into the basic redboot I get a massive amount of errors and debug codes... such as:

/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 0000c34f
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145

any ideas?
shadowandy
DD-WRT Novice


Joined: 23 Feb 2007
Posts: 11

PostPosted: Fri Feb 06, 2009 11:17    Post subject: Reply with quote
thanks to vcn and fluffy@prog.ru for the mem address of board_config!

Updated the Flashing DIR-300 back to original firmware

Have also created a tool for Generating DIR-300's board config
santiago_762000
DD-WRT Novice


Joined: 12 Jun 2009
Posts: 1

PostPosted: Fri Jun 12, 2009 19:40    Post subject: Ping response Reply with quote
Hello guys.
I have a similar problem. I have a D-Link wireless router model Dir-400. I flashed the router on weekend and it was OK. I was happy because some computer in my office and cell phones could access to Internet. Yesterday I tried to flash again the router following the same steps of the weekend but it didn't work. So I run the command bdrestore. I tried to ping the router but now I didn't receive any response from the device.

Any ideas?

With kind regards
Santiago
phpmysqlfreak
DD-WRT User


Joined: 29 Jun 2009
Posts: 63
Location: Germany, NRW

PostPosted: Sat Jul 11, 2009 18:19    Post subject: DIR-300, no connection after loading ap61.ram Reply with quote
Hello everyone,

I tried to play a bit with DD-Wrt/OpenWrt but now i need your help.

After flashing dd-wrt I noticed some failures at the wireless-things and the ses button.
I was hopefully, that openwrt has support of this, but there the same things happend.
OK, finally I decided to flash back the original firmware to start from the beginning.
The dd-wrt boot promt is now replaced with the original one:

Code:
RedBoot> version
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Version: "RedBoot v2.3"
RAM: 0x80000000-0x80800000, [0x80036350-0x807ed000] available
FLASH: 0xbfc00000 - 0xbfff0000, 64 blocks of 0x00010000 bytes each.
RedBoot>


The firmware does not come up and flashing the firmware from the inbuild-emergency webserver does not help at all.

When Im trying to load another bootload ( ap61.ram ), every tftp-server gives me some errors.
WinAgents TFTPServer 4 times out after transmitting 131072 bytes. PumpKIN times out after 164352 of 165108 bytes.

Some problems happened with the boardconfig, too. But with some reading in this forum they aren't there any more:

board config:
Code:
RedBoot> x -b 0xbfff0000 -l 0x27f
BFFF0000: 35 33 31 31 13 7D 00 04  41 74 68 65 72 6F 73 20  |5311.}..Atheros |
BFFF0010: 41 52 35 33 31 35 20 64  65 66 61 75 6C 74 00 00  |AR5315 default..|
BFFF0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0040: 00 00 00 00 00 00 00 00  00 01 00 00 00 00 02 39  |...............9|
BFFF0050: 00 06 00 07 0A F7 9E 00  05 7B CF 00 05 7B CF 00  |.........{...{..|
BFFF0060: 00 22 B0 97 98 39 00 22  B0 97 98 3A 00 80 C8 53  |."...9."...:...S|
BFFF0070: 11 02 00 13 00 00 00 80  C8 53 11 04 00 00 00 00  |.........S......|
BFFF0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF00A0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF00B0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF00C0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF00D0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF00E0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF00F0: 00 00 00 00 00 00 00 00  00 1C 16 8C 02 00 00 01  |................|
BFFF0100: 00 00 50 01 00 00 A0 62  16 8C 1C 0A 01 00 00 00  |..P....b........|
BFFF0110: 01 C2 00 02 C6 06 00 01  00 00 00 00 00 00 00 00  |................|
BFFF0120: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0130: 00 00 00 61 7F BF 00 03  00 00 00 00 00 00 00 00  |...a............|
BFFF0140: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0150: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0160: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
BFFF0170: 00 00 5A A5 00 00 00 00  03 13 49 43 20 53 71 04  |..Z.......IC Sq.|
BFFF0180: 12 02 04 00 03 06 00 01  00 00 05 00 41 0E 39 B1  |............A.9.|
BFFF0190: 1E B5 4E 2D 30 56 FF FF  E9 02 07 00 01 06 00 00  |..N-0V..........|
BFFF01A0: 01 00 15 00 07 52 41 01  68 74 72 65 73 6F 43 20  |.....RA.htresoC |
BFFF01B0: 6D 6F 75 6D 69 6E 61 63  69 74 6E 6F 2C 73 49 20  |mouminacitno,sI |
BFFF01C0: 63 6E 00 2E 52 41 30 35  31 30 30 2D 30 30 2D 30  |cn..RA05100-00-0|
BFFF01D0: 30 30 30 30 57 00 72 69  6C 65 73 65 20 73 41 4C  |0000W.rilese sAL|
BFFF01E0: 20 4E 65 52 65 66 65 72  63 6E 20 65 61 43 64 72  | NeRefercn eaCdr|
BFFF01F0: 30 00 00 30 00 FF 21 00  06 02 22 01 02 05 8D 80  |0..0..!...".....|
BFFF0200: 00 5B 05 22 40 02 89 54  22 00 02 05 1B 00 00 B7  |.[."@..T".......|
BFFF0210: 05 22 80 02 12 A8 22 01  02 05 36 00 01 6E 05 22  |."...."...6..n."|
BFFF0220: 00 02 25 51 22 02 02 05  6C 00 02 DC 05 22 80 02  |..%Q"...l...."..|
BFFF0230: 37 F9 22 03 02 05 A2 00  04 4A 02 22 08 03 08 22  |7."......J."..."|
BFFF0240: 06 04 61 00 BF 7F 03 00  02 22 01 05 00 FF 00 00  |..a......"......|
BFFF0250: 00 00 00 00 00 00 00 00  FF FF FF FF FF FF FF FF  |................|
BFFF0260: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0270: FF FF FF FF FF FF 00 00  D3 E3 50 03 A2 6E 00     |..........P..n. |
RedBoot>


behaviour after ap61.ram:

Code:
RedBoot> load ap61.ram
Using default protocol (TFTP)
Entry point: 0x800410bc, address range: 0x80041000-0x800680d8
RedBoot> go


Now the device has to come up at 192.168.1.1, but there is nothing at all. The connection with 192.168.20.81 was not terminated, even after 30 minutes.

Can anyone help me? I'm trying the things since 3 oder 4 weeks.

phpmysqlfreak

PS: sorry for my english, i'm a native german.
PPS: if you need any things to help me, let me know and i try to give them to you within 12 hours.
BlackWarrior
DD-WRT Novice


Joined: 09 Jan 2009
Posts: 31

PostPosted: Fri Oct 16, 2009 4:19    Post subject: Reply with quote
Quote:
I have a full dump of new (good) dir-300.

Hi! Can you send me this full dump on my e-mail? It is very necessary. I accidentally killed my DIR-300 and I want to flash it with jtag.
BlackWarrior
DD-WRT Novice


Joined: 09 Jan 2009
Posts: 31

PostPosted: Fri Oct 16, 2009 4:19    Post subject: Reply with quote
Quote:
I have a full dump of new (good) dir-300.

Hi! Can you send me this full dump on my e-mail? It is very necessary. I accidentally killed my DIR-300 and I want to flash it with jtag.
Domino_55
DD-WRT User


Joined: 15 Sep 2008
Posts: 88

PostPosted: Fri Oct 16, 2009 7:29    Post subject: Reply with quote
BlackWarrior wrote:
Quote:
I have a full dump of new (good) dir-300.

Hi! Can you send me this full dump on my e-mail? It is very necessary. I accidentally killed my DIR-300 and I want to flash it with jtag.


I recommend to you that doesn't try to full flash via jtag because for this method need a very long time (few days). Only flash the redboot. After the flash your device will boot up and starting the bootloader. Now at this point possible to flash the firmware via the redboot about 10-15 mins.
BlackWarrior
DD-WRT Novice


Joined: 09 Jan 2009
Posts: 31

PostPosted: Fri Oct 16, 2009 11:16    Post subject: Reply with quote
Domino_55 wrote:
BlackWarrior wrote:
Quote:
I have a full dump of new (good) dir-300.

Hi! Can you send me this full dump on my e-mail? It is very necessary. I accidentally killed my DIR-300 and I want to flash it with jtag.


I recommend to you that doesn't try to full flash via jtag because for this method need a very long time (few days). Only flash the redboot. After the flash your device will boot up and starting the bootloader. Now at this point possible to flash the firmware via the redboot about 10-15 mins.
Ok. But where can I download the original redboot and how do I properly fill (which should run)?
ps2chiper
DD-WRT Novice


Joined: 06 Feb 2009
Posts: 10

PostPosted: Mon Nov 16, 2009 19:45    Post subject: Reply with quote
I followed the steps after I used jffs and nuked the board configuration. I was successful at restoring the original dlink firmware, but I am unable to restore the dd-wrt firmware. I run into this error No radio config data found! Any advice?
laharl2k
DD-WRT Novice


Joined: 23 Nov 2009
Posts: 4

PostPosted: Mon Nov 23, 2009 21:02    Post subject: Reply with quote
I had the same error, i activated de jffs without knowing that it nukes the board config and now i can't load the firmware.

THIS IS A SERIOUS BUG, SOMEONE AT LEAST DELETE THE JFFS OPTION FROM THE DIR-300 FIRMWARE SO THIS WON'T HAPPEN TO MORE PEOPLE

Can someone how knows how to FIX this, i mean to restore it without "no radio" etc. at least make a entry in the wiki, let's say "unnuke dir-300 board config from jffs bug"?

EDIT:
I just fixed mine, just do this:
http://www.shadowandy.net/2009/02/generating-dir-300s-board-config.htm
then
http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm
and then flash back to dd-wrt
http://www.shadowandy.net/2007/09/mini-flashing-guide-for-dir-300.htm

in my case the firmware settings were as just before bricking, so just disabled the JFFS option and saved, and made a backup of the NVRAM from the menu just that.
Hope this helps someone.
cedwifi
DD-WRT Novice


Joined: 11 Jan 2010
Posts: 2

PostPosted: Mon Jan 11, 2010 20:37    Post subject: Reply with quote
I got exactly the same issue ! And I just fixed as you so :
http://www.shadowandy.net/2009/02/generating-dir-300s-board-config.htm
then
http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm
and then flash back to dd-wrt
http://www.shadowandy.net/2007/09/mini-flashing-guide-for-dir-300.htm


I think too that :
THIS IS A SERIOUS BUG, SOMEONE AT LEAST DELETE THE JFFS OPTION FROM THE DIR-300 FIRMWARE SO THIS WON'T HAPPEN TO MORE PEOPLE

Thank you for you advise.

Hope someone could help the future people whish have this bug by simply regenerate on board setting ?
Goto page Previous  1, 2, 3, 4  Next Display posts from previous:    Page 3 of 4
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC 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 cannot attach files in this forum
You cannot download files in this forum