TP-Link Archer C9 v3? (EU)

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, 7, 8, 9, 10  Next
Author Message
TheDoc
DD-WRT Novice


Joined: 25 Dec 2006
Posts: 16

PostPosted: Wed Feb 07, 2018 15:49    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
!asdf wrote:

Hey,

thank you for your response
my situation seems similar to ZaphodB73s:
initially i was on
Archer_C9(EU)_V4_161018_1479287836363l stock
went to
10-17-2017-r33525/factory-to-ddwrt.bin
via webflash
after confirming dd-wrt webgui and changing admin user & pass
i went for
01-31-2018-r34777/archer-c9v4-webflash.bin
via dd-wrt webflash, it did fine, until 300sec reboot timeout
and from there I also got the "dreaded WPS led"

please find attached a log as verbose as i could make,
the C9-V3-Fix-R5_v2.bin is just with patched MAC-Address

cheers


I'll make it a weekend project to get a EU version of TP-LIINK to load, bring it up to 34777 and try to recover it.

The last test to try beforehand would be loading C9-V3-Fix-R5.bin without changing the MAC address.

Request for aid: A person with a working C9 V4 EU router can help by providing some information. SSH into the unit and save the results of these commands:
dd if=/dev/mtd1 skip=14912 bs=1024 count=1 | hexdump -C
dd if=/dev/mtd1 skip=14936 bs=1024 count=1 | hexdump -C

A unit with TP-LINK firmware is best. However, a working unit with DD-WRT will suffice.

Thanks,

Doc
Sponsor
!asdf
DD-WRT Novice


Joined: 03 Feb 2018
Posts: 5

PostPosted: Wed Feb 07, 2018 20:52    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
TheDoc wrote:
!asdf wrote:

Hey,

thank you for your response
my situation seems similar to ZaphodB73s:
initially i was on
Archer_C9(EU)_V4_161018_1479287836363l stock
went to
10-17-2017-r33525/factory-to-ddwrt.bin
via webflash
after confirming dd-wrt webgui and changing admin user & pass
i went for
01-31-2018-r34777/archer-c9v4-webflash.bin
via dd-wrt webflash, it did fine, until 300sec reboot timeout
and from there I also got the "dreaded WPS led"

please find attached a log as verbose as i could make,
the C9-V3-Fix-R5_v2.bin is just with patched MAC-Address

cheers


I'll make it a weekend project to get a EU version of TP-LIINK to load, bring it up to 34777 and try to recover it.

The last test to try beforehand would be loading C9-V3-Fix-R5.bin without changing the MAC address.

Request for aid: A person with a working C9 V4 EU router can help by providing some information. SSH into the unit and save the results of these commands:
dd if=/dev/mtd1 skip=14912 bs=1024 count=1 | hexdump -C
dd if=/dev/mtd1 skip=14936 bs=1024 count=1 | hexdump -C

A unit with TP-LINK firmware is best. However, a working unit with DD-WRT will suffice.

Thanks,

Doc


Hey,

i went for your last advice and flashed the unmodified fix C9-V3-Fix-R5.bin
after that a reboot with pressed wps-button
and it took the Archer_C9(EU)_V4_161018_1479287836363l renamed as ArcherC9v3_tp_recovery.bin

attached is the log of the successful flash
also a screenshot of hex modified C9-V3-Fix-R5_v2.bin that did not work.
as well as a bad photo of Serial-Console Pinout from TP-LINK Archer C9 V4 EU since i have not found any when i searched for it:

from left to right on the router-board
1. not connected: 3.3V
2. grey: ground
3. violet: RX
4. blue: TX

connected to USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter https://www.amazon.co.uk/gp/product/B00AFRXKFU
from front to back
1. grey : ground
4. violet: TX
5. blue: RX

Thank You!
TheDoc
DD-WRT Novice


Joined: 25 Dec 2006
Posts: 16

PostPosted: Wed Feb 07, 2018 21:58    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
!asdf wrote:


Hey,

i went for your last advice and flashed the unmodified fix C9-V3-Fix-R5.bin
after that a reboot with pressed wps-button
and it took the Archer_C9(EU)_V4_161018_1479287836363l renamed as ArcherC9v3_tp_recovery.bin

attached is the log of the successful flash
also a screenshot of hex modified C9-V3-Fix-R5_v2.bin that did not work.
as well as a bad photo of Serial-Console Pinout from TP-LINK Archer C9 V4 EU since i have not found any when i searched for it:

from left to right on the router-board
1. not connected: 3.3V
2. grey: ground
3. violet: RX
4. blue: TX

connected to USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter https://www.amazon.co.uk/gp/product/B00AFRXKFU
from front to back
1. grey : ground
4. violet: TX
5. blue: RX

Thank You!


Great! It looks like the hex editor inserted the 6 bytes of the MAC address. Looking at address E there is a AA and at address F there is a BB (and so on for the 6 bytes.) Those values were originally at address 8 and 9. The hex editor needs to be in overwrite mode. The entire file shifted up by 6 bytes which places data at the wrong addresses. You can do the procedure again with a corrected file and your MAC address will be back to your original value. You should recover with TP-LINK again after loading the fix file.
!asdf
DD-WRT Novice


Joined: 03 Feb 2018
Posts: 5

PostPosted: Wed Feb 07, 2018 22:50    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
TheDoc wrote:
!asdf wrote:


Hey,

i went for your last advice and flashed the unmodified fix C9-V3-Fix-R5.bin
after that a reboot with pressed wps-button
and it took the Archer_C9(EU)_V4_161018_1479287836363l renamed as ArcherC9v3_tp_recovery.bin

attached is the log of the successful flash
also a screenshot of hex modified C9-V3-Fix-R5_v2.bin that did not work.
as well as a bad photo of Serial-Console Pinout from TP-LINK Archer C9 V4 EU since i have not found any when i searched for it:

from left to right on the router-board
1. not connected: 3.3V
2. grey: ground
3. violet: RX
4. blue: TX

connected to USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter https://www.amazon.co.uk/gp/product/B00AFRXKFU
from front to back
1. grey : ground
4. violet: TX
5. blue: RX

Thank You!


Great! It looks like the hex editor inserted the 6 bytes of the MAC address. Looking at address E there is a AA and at address F there is a BB (and so on for the 6 bytes.) Those values were originally at address 8 and 9. The hex editor needs to be in overwrite mode. The entire file shifted up by 6 bytes which places data at the wrong addresses. You can do the procedure again with a corrected file and your MAC address will be back to your original value. You should recover with TP-LINK again after loading the fix file.


oh my..,
its all right there in the screenshot..., the INS in the corner and the suspicious AABBCCCCBBAA right behind the MAC...

directly after the fix i did TFTP-recover to TP-LINKs Archer_C9(EU)_V4_161018.

from there again via
10-17-2017-r33525\factory-to-ddwrt.bin
to now DD-WRT v3.0-r33986 std (12/04/17)
interestingly enough without reflashing the MAC is already correct... i.e. not AA-BB-CC-CC-BB-AA

is there any information on later builds or known good upgrade-path to for ex. https://www.dd-wrt.com/site/support/other-downloads?path=betas%2F2018%2F01-31-2018-r34777%2Ftplink_archer-c9v4%2F ?
Malachi
DD-WRT Guru


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

PostPosted: Wed Feb 07, 2018 23:23    Post subject: Reply with quote
Smaller pictures.
_________________
I am far from a guru, I'm barely a novice.
ZaphodB73
DD-WRT Novice


Joined: 06 Feb 2018
Posts: 8

PostPosted: Thu Feb 08, 2018 12:50    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
TheDoc wrote:
!asdf wrote:

Hey,

thank you for your response
my situation seems similar to ZaphodB73s:
initially i was on
Archer_C9(EU)_V4_161018_1479287836363l stock
went to
10-17-2017-r33525/factory-to-ddwrt.bin
via webflash
after confirming dd-wrt webgui and changing admin user & pass
i went for
01-31-2018-r34777/archer-c9v4-webflash.bin
via dd-wrt webflash, it did fine, until 300sec reboot timeout
and from there I also got the "dreaded WPS led"

please find attached a log as verbose as i could make,
the C9-V3-Fix-R5_v2.bin is just with patched MAC-Address

cheers


I'll make it a weekend project to get a EU version of TP-LIINK to load, bring it up to 34777 and try to recover it.

The last test to try beforehand would be loading C9-V3-Fix-R5.bin without changing the MAC address.

Request for aid: A person with a working C9 V4 EU router can help by providing some information. SSH into the unit and save the results of these commands:
dd if=/dev/mtd1 skip=14912 bs=1024 count=1 | hexdump -C
dd if=/dev/mtd1 skip=14936 bs=1024 count=1 | hexdump -C

A unit with TP-LINK firmware is best. However, a working unit with DD-WRT will suffice.

Thanks,

Doc


Here is a dump from a successfully recovered EU v4 Archer C9 running 2017-12-04 r33986 release.

See attached file.....

Regards, ZaphodB73



xxx_dd-wrt.txt
 Description:
Requested dump

Download
 Filename:  xxx_dd-wrt.txt
 Filesize:  5.76 KB
 Downloaded:  627 Time(s)

TheDoc
DD-WRT Novice


Joined: 25 Dec 2006
Posts: 16

PostPosted: Thu Feb 08, 2018 15:05    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
ZaphodB73 wrote:


Here is a dump from a successfully recovered EU v4 Archer C9 running 2017-12-04 r33986 release.

See attached file.....

Regards, ZaphodB73


Thank you!
ZaphodB73
DD-WRT Novice


Joined: 06 Feb 2018
Posts: 8

PostPosted: Thu Feb 08, 2018 15:35    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
TheDoc wrote:
ZaphodB73 wrote:


Here is a dump from a successfully recovered EU v4 Archer C9 running 2017-12-04 r33986 release.

See attached file.....

Regards, ZaphodB73


Thank you!


You are welcome, let me know if there is anything else I can help with....

Regards, ZaphodB73
ek
DD-WRT Novice


Joined: 08 Dec 2017
Posts: 2

PostPosted: Sun Feb 11, 2018 11:29    Post subject: Reply with quote
Thanks TheDoc for C9-V3-Fix-R5 and instructions, also !asdf for tip the Archer_C9(EU)_V4_161018_1479287836363 stock version was successful. I got back my V3 EU after jffs disaster.

My experience:
C9-V3-Fix-R5 worked for me, but I was not able to install of V3 stock FW (I tried latest two). It starts to reboot every 10 second and reason was something like unable mounting FS.

Archer_C9(EU)_V4 was successful, thanks !asdf.

I tried go back to DD-WRT, but found only latest factory-to-ddwrt (from october 2017) firmware in this forum. Still, it was successful. Then I tried to update latest beta update 02-10-2018-r34886 > tplink_archer-c9v3 > archer-c9v3-webflash, but it starts to restart every 10s with mounting trouble again.

BTW, I had often to apply C9-V3-Fix-R5 again, caused by factory bootcheck fail, after almost every new FW.

Can somebody suggest DD-WRT build could work, later factory-to-ddwrt from this forum? I need 5G Wifi, OpenVPN and SSH for port forward.

Thanks!
Sadguy
DD-WRT Novice


Joined: 23 Oct 2017
Posts: 7

PostPosted: Mon Feb 19, 2018 18:04    Post subject: Reply with quote
TheDoc wrote:

An updated procedure has been posted to this thread. It was tested against 34080.

Thank you very much for your help. I have also tested C9-V3-Fix-R5 and it works for 34311 and 34080.
Magician1981
DD-WRT Novice


Joined: 25 Feb 2018
Posts: 2

PostPosted: Sun Feb 25, 2018 20:26    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
!asdf wrote:
TheDoc wrote:
!asdf wrote:


Hey,

i went for your last advice and flashed the unmodified fix C9-V3-Fix-R5.bin
after that a reboot with pressed wps-button
and it took the Archer_C9(EU)_V4_161018_1479287836363l renamed as ArcherC9v3_tp_recovery.bin

attached is the log of the successful flash
also a screenshot of hex modified C9-V3-Fix-R5_v2.bin that did not work.
as well as a bad photo of Serial-Console Pinout from TP-LINK Archer C9 V4 EU since i have not found any when i searched for it:

from left to right on the router-board
1. not connected: 3.3V
2. grey: ground
3. violet: RX
4. blue: TX

connected to USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter https://www.amazon.co.uk/gp/product/B00AFRXKFU
from front to back
1. grey : ground
4. violet: TX
5. blue: RX

Thank You!


Great! It looks like the hex editor inserted the 6 bytes of the MAC address. Looking at address E there is a AA and at address F there is a BB (and so on for the 6 bytes.) Those values were originally at address 8 and 9. The hex editor needs to be in overwrite mode. The entire file shifted up by 6 bytes which places data at the wrong addresses. You can do the procedure again with a corrected file and your MAC address will be back to your original value. You should recover with TP-LINK again after loading the fix file.


oh my..,
its all right there in the screenshot..., the INS in the corner and the suspicious AABBCCCCBBAA right behind the MAC...

directly after the fix i did TFTP-recover to TP-LINKs Archer_C9(EU)_V4_161018.

from there again via
10-17-2017-r33525\factory-to-ddwrt.bin
to now DD-WRT v3.0-r33986 std (12/04/17)
interestingly enough without reflashing the MAC is already correct... i.e. not AA-BB-CC-CC-BB-AA

is there any information on later builds or known good upgrade-path to for ex. https://www.dd-wrt.com/site/support/other-downloads?path=betas%2F2018%2F01-31-2018-r34777%2Ftplink_archer-c9v4%2F ?



Hello everyone,

So I did the exact same thing as above, but my mac adress is still on AA-BB etc..
Is there a way to change it to the one that is on the back of the router? Running r33986 currently.
I've tried to re-apply the C9-V3-Fix-R5_v2.bin file (modified with hex editor) using serial interface but I have no idea how to enter cfe command after the bootup process (at the login prompt).

Thanx in advance
ZaphodB73
DD-WRT Novice


Joined: 06 Feb 2018
Posts: 8

PostPosted: Mon Feb 26, 2018 5:53    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
Magician1981 wrote:
!asdf wrote:
TheDoc wrote:
!asdf wrote:


Hey,

i went for your last advice and flashed the unmodified fix C9-V3-Fix-R5.bin
after that a reboot with pressed wps-button
and it took the Archer_C9(EU)_V4_161018_1479287836363l renamed as ArcherC9v3_tp_recovery.bin

attached is the log of the successful flash
also a screenshot of hex modified C9-V3-Fix-R5_v2.bin that did not work.
as well as a bad photo of Serial-Console Pinout from TP-LINK Archer C9 V4 EU since i have not found any when i searched for it:

from left to right on the router-board
1. not connected: 3.3V
2. grey: ground
3. violet: RX
4. blue: TX

connected to USB 2.0 to TTL UART 6PIN CP2102 Module Serial Converter https://www.amazon.co.uk/gp/product/B00AFRXKFU
from front to back
1. grey : ground
4. violet: TX
5. blue: RX

Thank You!


Great! It looks like the hex editor inserted the 6 bytes of the MAC address. Looking at address E there is a AA and at address F there is a BB (and so on for the 6 bytes.) Those values were originally at address 8 and 9. The hex editor needs to be in overwrite mode. The entire file shifted up by 6 bytes which places data at the wrong addresses. You can do the procedure again with a corrected file and your MAC address will be back to your original value. You should recover with TP-LINK again after loading the fix file.


oh my..,
its all right there in the screenshot..., the INS in the corner and the suspicious AABBCCCCBBAA right behind the MAC...

directly after the fix i did TFTP-recover to TP-LINKs Archer_C9(EU)_V4_161018.

from there again via
10-17-2017-r33525\factory-to-ddwrt.bin
to now DD-WRT v3.0-r33986 std (12/04/17)
interestingly enough without reflashing the MAC is already correct... i.e. not AA-BB-CC-CC-BB-AA

is there any information on later builds or known good upgrade-path to for ex. https://www.dd-wrt.com/site/support/other-downloads?path=betas%2F2018%2F01-31-2018-r34777%2Ftplink_archer-c9v4%2F ?



Hello everyone,

So I did the exact same thing as above, but my mac adress is still on AA-BB etc..
Is there a way to change it to the one that is on the back of the router? Running r33986 currently.
I've tried to re-apply the C9-V3-Fix-R5_v2.bin file (modified with hex editor) using serial interface but I have no idea how to enter cfe command after the bootup process (at the login prompt).

Thanx in advance


You have to hit enter to interrupt the boot process in the very first seconds of the boot if you want to have access to the CFE prompt.....

Regards, ZaphodB73
TheDoc
DD-WRT Novice


Joined: 25 Dec 2006
Posts: 16

PostPosted: Wed Feb 28, 2018 14:32    Post subject: Re: Try this to recover from bad builds and jffs2 Reply with quote
ZaphodB73 wrote:
You have to hit enter to interrupt the boot process in the very first seconds of the boot if you want to have access to the CFE prompt.....

Regards, ZaphodB73


That should work. I've been holding down ctrl-C during the reboot process. I end up with a long series of ctrl-C's on the terminal but they don't hurt anything. The window to stop the boot process in CFE seems small.

After redoing the flashing of C9-V3-Fix-R5, be safe do a full recovery of the stock TP-LINK firmware again.

Not recommended but will work: If you have trouble stopping the boot process in CFE load the version of DD-WRT that previously corrupted your unit. Once the unit is corrupted, it stops in CFE because of the corruption.
Magician1981
DD-WRT Novice


Joined: 25 Feb 2018
Posts: 2

PostPosted: Wed Feb 28, 2018 20:51    Post subject: Reply with quote
Ok guys,

thanx for helping me out. I've managed to ''unbrick'' my C9 multiple times now. There is still one problem however! The MAC adress is stuck on AA-BB etc. Even after a hex editing of the R5 file. I've double checked if the file was saved correctly with a different editor and the desired MAC adress is in the correct ''offset'' line as described in earlier posts. Any ideas??
Here is the current serial output:

-------------------------------------------------------

Digital core power voltage set to 1.0V
Decompressing(LZMA inbase:0x1e024004)...done
Digital core power voltage set to 1.0V

SHMOO VER 1.13

PKID07DC06011801080000000000001A103F01000000

S300001D3
000013F0


RDLYW0 00000004

RDENW0 00000033

RDQSW0

0000000000111111111122222222223333333333444444444455555555556666
0123456789012345678901234567890123456789012345678901234567890123
00 ----------------++++++++++++++++++++++++X+++++++++++++++++++++--
01 -------------------++++++++++++++++++++++X++++++++++++++++++++++
02 -------------+++++++++++++++++++++++X++++++++++++++++++++++-----
03 ---------------+++++++++++++++++++++++X++++++++++++++++++++++---
04 ---------+++++++++++++++++++++++X+++++++++++++++++++++++--------
05 ---------------+++++++++++++++++++++++X++++++++++++++++++++++---
06 -------------++++++++++++++++++++X++++++++++++++++++++----------
07 ------------------+++++++++++++++++++++++X++++++++++++++++++++++
08 ------++++++++++++++++++++++++X+++++++++++++++++++++++----------
09 ---------++++++++++++++++++++++++X++++++++++++++++++++++++------
10 ---++++++++++++++++++++++++X++++++++++++++++++++++++------------
11 -----------+++++++++++++++++++++++X+++++++++++++++++++++++------
12 -----++++++++++++++++++++++++X+++++++++++++++++++++++-----------
13 -----------+++++++++++++++++++++++X+++++++++++++++++++++++------
14 ---------+++++++++++++++++++++++X+++++++++++++++++++++++--------
15 ----------+++++++++++++++++++++++X+++++++++++++++++++++++-------


PW0

0000000000111111111122222222223333333333444444444455555555556666
0123456789012345678901234567890123456789012345678901234567890123
00 -----------------+++++++++++++++++++++++X+++++++++++++++++++++++
01 -------------------++++++++++++++++++++++X++++++++++++++++++++++
02 ------------++++++++++++++++++++++++++X+++++++++++++++++++++++--
03 ----------------++++++++++++++++++++++++X+++++++++++++++++++++--
04 ---------+++++++++++++++++++++++X+++++++++++++++++++++++--------
05 ---------------+++++++++++++++++++++++X++++++++++++++++++++++---
06 -------------+++++++++++++++++++++X++++++++++++++++++++---------
07 ------------------+++++++++++++++++++++++X++++++++++++++++++++++
08 ------++++++++++++++++++++++++X+++++++++++++++++++++++----------
09 ---------++++++++++++++++++++++++X++++++++++++++++++++++++------
10 ---++++++++++++++++++++++++X++++++++++++++++++++++++------------
11 ----------++++++++++++++++++++++++X+++++++++++++++++++++++------
12 ------+++++++++++++++++++++++X+++++++++++++++++++++++-----------
13 -----------+++++++++++++++++++++++X+++++++++++++++++++++++------
14 ---------+++++++++++++++++++++++X+++++++++++++++++++++++--------
15 ----------+++++++++++++++++++++++X+++++++++++++++++++++++-------


NW0

0000000000111111111122222222223333333333444444444455555555556666
0123456789012345678901234567890123456789012345678901234567890123
00 -------++++++++++++++++++++++++++++X++++++++++++++++++++++++++--
01 -----------++++++++++++++++++++++++++X++++++++++++++++++++++++++
02 -----+++++++++++++++++++++++++++X++++++++++++++++++++++++++-----
03 -------+++++++++++++++++++++++++++X++++++++++++++++++++++++++---
04 ++++++++++++++++++++++++++++X+++++++++++++++++++++++++++--------
05 -----++++++++++++++++++++++++++++X+++++++++++++++++++++++++++---
06 ---+++++++++++++++++++++++++X+++++++++++++++++++++++++----------
07 ---------+++++++++++++++++++++++++++X++++++++++++++++++++++++++-
08 -+++++++++++++++++++++++++++X++++++++++++++++++++++++++---------
09 ----+++++++++++++++++++++++++++X+++++++++++++++++++++++++++-----
10 ++++++++++++++++++++++++++X++++++++++++++++++++++++++-----------
11 -----+++++++++++++++++++++++++++X+++++++++++++++++++++++++++----
12 -+++++++++++++++++++++++++++X++++++++++++++++++++++++++---------
13 ------+++++++++++++++++++++++++++X++++++++++++++++++++++++++----
14 ---++++++++++++++++++++++++++X++++++++++++++++++++++++++--------
15 -----++++++++++++++++++++++++++X++++++++++++++++++++++++++------


WRDQW0

0000000000111111111122222222223333333333444444444455555555556666
0123456789012345678901234567890123456789012345678901234567890123
00 ++++++++++++++++++++++++X+++++++++++++++++++++++-----++++++++++-
01 ++++++++++++++++++++++++X++++++++++++++++++++++++------++++++++-
02 +++++++++++++++++++++++X+++++++++++++++++++++++-----+++++++++++-
03 ++++++++++++++++++++++++X+++++++++++++++++++++++------+++++++++-
04 +++++++++++++++++++++X+++++++++++++++++++++----------++++++++++-
05 ++++++++++++++++++++++++X+++++++++++++++++++++++------+++++++++-
06 ++++++++++++++++++++++X++++++++++++++++++++++--------++++++++++-
07 ++++++++++++++++++++++++X+++++++++++++++++++++++-----++++++++++-
08 +++++++++++++++++++++X++++++++++++++++++++----------+++++++++++-
09 +++++++++++++++++++++++X++++++++++++++++++++++-------++++++++++-
10 ++++++++++++++++++++X+++++++++++++++++++--------------+++++++++-
11 ++++++++++++++++++++++++X+++++++++++++++++++++++-----++++++++++-
12 +++++++++++++++++++++X+++++++++++++++++++++---------+++++++++++-
13 +++++++++++++++++++++++X++++++++++++++++++++++-------++++++++++-
14 +++++++++++++++++++++X+++++++++++++++++++++----------++++++++++-
15 +++++++++++++++++++++++X++++++++++++++++++++++--------+++++++++-


WRDMW0 00000023
WRDMW0 00000022


ADDR

0000000000111111111122222222223333333333444444444455555555556666
0123456789012345678901234567890123456789012345678901234567890123
00 +++++++++++++++++++S+++++++++++X++++++++++++++++++++++++++++++++

Decompressing(LZMA inbase:0x1e024004)...done


CFE version 6.37.14.93 (r469350) based on BBP 1.0.37 for BCM947XX (32bit,SP,)
Build Date: Wed Jan 13 15:52:58 UTC 2016 (leven@leven)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
DDR Clock: 800 MHz
Info: DDR frequency set from clkfreq=1000,*800*
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.93 (r469350)
CPU type 0x0: 1000MHz
Tot mem: 131072 KBytes

CFE mem: 0x00F00000 - 0x02F8E8A8 (34138280)
Data: 0x00F50380 - 0x00F556C0 (21312)
BSS: 0x00F556D0 - 0x00F8C8A8 (225752)
Heap: 0x00F8C8A8 - 0x02F8C8A8 (33554432)
Stack: 0x02F8C8A8 - 0x02F8E8A8 (8192)
Text: 0x00F00000 - 0x00F4617C (287100)

Device eth0: hwaddr AA-BB-CC-CC-BB-AA, ipaddr 192.168.0.1, mask 255.255.255.0
gateway not set, nameserver not set
Reading Partition Table from NVRAM ... OK
Parsing Partition Table ... OK
factory boot check integer ok.
factory boot load fs boot len 262144 to addr 0x3f00000.
Closing network.
Starting program at 0x03f00000
Decompressing(LZMA inbase:0x1e064004)...done


CFE version 6.37.14.93 (r469350) based on BBP 1.0.37 for BCM947XX (32bit,SP,)
Build Date: Fri Jul 22 09:27:53 UTC 2016 (leven@leven)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
DDR Clock: 800 MHz
Info: DDR frequency set from clkfreq=1000,*800*
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.93 (r469350)
CPU type 0x0: 1000MHz
Tot mem: 131072 KBytes

CFE mem: 0x00F00000 - 0x02F88BC8 (34114504)
Data: 0x00F4F8BC - 0x00F4FF18 (1628)
BSS: 0x00F4FF28 - 0x00F86BC8 (224416)
Heap: 0x00F86BC8 - 0x02F86BC8 (33554432)
Stack: 0x02F86BC8 - 0x02F88BC8 (8192)
Text: 0x00F00000 - 0x00F45258 (283224)

Device eth0: hwaddr AA-BB-CC-CC-BB-AA, ipaddr 192.168.0.1, mask 255.255.255.0
gateway not set, nameserver not set
Boot program checksum is invalid
flash0.0: Device not found
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: ... 1638024 bytes read
Entry at 0x00008000
Closing network.
Starting program at 0x00008000
Uncompressing Linux... done, booting the kernel.
** 22 printk messages dropped ** Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 124244K/131072K available (3438K kernel code, 192K rwdata, 1208K rodata, 344K init, 371K bss, 6828K reserved, 0K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0x88800000 - 0xff800000 (1904 MB)
lowmem : 0x80000000 - 0x88000000 ( 128 MB)
pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
modules : 0x7f000000 - 0x7fe00000 ( 14 MB)
.text : 0x80008000 - 0x80491e34 (4648 kB)
.init : 0x80492000 - 0x804e8000 ( 344 kB)
.data : 0x804e8000 - 0x805182f4 ( 193 kB)
.bss : 0x8051b000 - 0x80577f78 ( 372 kB)
Hierarchical RCU implementation.
CONFIG_RCU_FANOUT set to non-default value of 2
Build-time adjustment of leaf fanout to 2.
NR_IRQS:256
MPCORE GIC init
soc_dmu_init
add clk lookups
MPCORE Global Timer Clock 500000000Hz on IRQ 27
sched_clock: 32 bits at 500MHz, resolution 2ns, wraps every 4294967295ns
clocksource: mpcore_gtimer: mask: 0xffffffffffffffff max_cycles: 0xe6a171a037, max_idle_ns: 881590485102 ns
register local timer
smp_twd: clock not found -2
Calibrating local timer... 499.73MHz.
Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
2 cores has been found
Setting up static identity map for 0x85e0 - 0x8614
L2C: platform provided aux values permit register corruption.
L2C: DT/platform modifies aux control register: 0x0a130000 -> 0x7a530000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 16 ways, 256 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x4e530001
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Brought up 2 CPUs
SMP: Total of 2 processors activated (3981.31 BogoMIPS).
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 3, 32768 bytes)
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
coherence_win_size = 10000000
coherence_flag = FFFFFFF8
ddr_phys_offset_va =FFFFFFFF
ddr_phys_offset2_va =A8000000
Found a ST compatible (Winbond/NexFlash) serial flash with 256 64KB blocks; total size 16MB
found cfe nvram on sflash
CCA UART Clock Config: Sel=1 Ovr=1 Div=48
CCA UART Clock rate 125000000Hz CCB UART Clock rate 125000000Hz
clocksource: Switched to clocksource mpcore_gtimer
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
init gpio code
PCI: no core
PCI: no core
PCI: scanning bus 0
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffffffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
PCI: Fixing up bus 0 domain 0
PCIE1 link=1
PCIE1 switching to GEN2
PCIE1 link=1
PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
PCI: Fixing up bus 0 domain 1
PCI: bus0: Fast back to back transfers disabled
pci 0001:01:00.0: Max Payload Size set to 512 (was 128, max 512)
PCI: Fixing up bus 1 domain 1
PCI: bus1: Fast back to back transfers disabled
pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
pci 0001:00:00.0: PCI bridge to [bus 01]
pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
PCIE2 link=1
PCIE2 switching to GEN2
PCIE2 link=1
PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [mem 0x40000000-0x47ffffff]
pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
PCI: Fixing up bus 0 domain 2
PCI: bus0: Fast back to back transfers disabled
pci 0002:01:00.0: Max Payload Size set to 512 (was 128, max 512)
PCI: Fixing up bus 1 domain 2
PCI: bus1: Fast back to back transfers disabled
pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
pci 0002:01:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
pci 0002:00:00.0: PCI bridge to [bus 01]
pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff]
PCIE3 link=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
io scheduler noop registered (default)
io scheduler cfq registered
serial8250_init
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
console [ttyS0] disabled
serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117, base_baud = 7812500) is a 16550
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117, base_baud = 7812500) is a 16550
brd: module loaded
loop: module loaded
bcmsflash: squash filesystem found at block 34
Creating 6 MTD partitions on "bcmsflash":
0x000000000000-0x000000080000 : "boot"
0x000000080000-0x000000ff0000 : "linux"
0x000000220000-0x000000f40000 : "rootfs"
0x000000f40000-0x000000ff0000 : "ddwrt"
0x000000ff0000-0x000001000000 : "nvram_cfe"
0x000000fe0000-0x000000ff0000 : "nvram"
nflash: found no supported devices
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
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 (1941 buckets, 7764 max)
nf_conntrack_rtsp v0.7 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.7 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Registering SWP/SWPB emulation handler
found cfe nvram
check if nvram copy is required CFE Size is 65536
nvram copy magic is 48534C46
max nvram space = 131072
read 65536 bytes to offset 0
Key type encrypted registered
Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
brcmnand: found no supported devices
squashfs: SQUASHFS error: unable to read id index table
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:
0100 4096 ram0 (driver?)
0101 4096 ram1 (driver?)
0102 4096 ram2 (driver?)
0103 4096 ram3 (driver?)
0104 4096 ram4 (driver?)
0105 4096 ram5 (driver?)
0106 4096 ram6 (driver?)
0107 4096 ram7 (driver?)
0108 4096 ram8 (driver?)
0109 4096 ram9 (driver?)
010a 4096 ram10 (driver?)
010b 4096 ram11 (driver?)
010c 4096 ram12 (driver?)
010d 4096 ram13 (driver?)
010e 4096 ram14 (driver?)
010f 4096 ram15 (driver?)
1f00 512 mtdblock0 (driver?)
1f01 15808 mtdblock1 (driver?)
1f02 13440 mtdblock2 (driver?)
1f03 704 mtdblock3 (driver?)
1f04 64 mtdblock4 (driver?)
1f05 64 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
CPU1: stopping
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.116-rc1 #2610
Hardware name: Northstar Prototype
Backtrace:
[<8001b950>] (dump_backtrace) from [<8001bbd8>] (show_stack+0x18/0x1c)
r7:87853f58 r6:60000193 r5:00000000 r4:80508220
[<8001bbc0>] (show_stack) from [<8015e6f4>] (dump_stack+0x8c/0xa0)
[<8015e668>] (dump_stack) from [<8001d754>] (handle_IPI+0x110/0x1a8)
r7:87853f58 r6:00000001 r5:00000000 r4:8051b1a0
[<8001d644>] (handle_IPI) from [<80009394>] (gic_handle_irq+0x78/0x7c)
r7:b0100100 r6:87853f58 r5:b010010c r4:804f7b1c
[<8000931c>] (gic_handle_irq) from [<80009ea0>] (__irq_svc+0x40/0x54)
Exception stack(0x87853f58 to 0x87853fa0)
3f40: 87eeb248 00000000
3f60: 00000578 8000a9c0 87852000 804f78e0 8042be9c 804e4224 87853fc8 413fc090
3f80: 00000000 87853fb4 87853fb8 87853fa8 80019564 80019568 60000013 ffffffff
r9:413fc090 r8:87853fc8 r7:87853f8c r6:ffffffff r5:60000013 r4:80019568
[<8001952c>] (arch_cpu_idle) from [<8006c2ac>] (default_idle_call+0x30/0x34)
[<8006c27c>] (default_idle_call) from [<8006c3b8>] (cpu_startup_entry+0x108/0x13c)
[<8006c2b0>] (cpu_startup_entry) from [<8001d40c>] (secondary_start_kernel+0x150/0x158)
r7:8051b180 r4:80505920
[<8001d2bc>] (secondary_start_kernel) from [<00009428>] (0x9428)
r5:00000055 r4:0782c06a
Rebooting in 10 seconds..

-----------------------------------------------------
TheDoc
DD-WRT Novice


Joined: 25 Dec 2006
Posts: 16

PostPosted: Thu Mar 01, 2018 13:42    Post subject: Reply with quote
Magician1981 wrote:
Ok guys,

thanx for helping me out. I've managed to ''unbrick'' my C9 multiple times now. There is still one problem however! The MAC adress is stuck on AA-BB etc. Even after a hex editing of the R5 file. I've double checked if the file was saved correctly with a different editor and the desired MAC adress is in the correct ''offset'' line as described in earlier posts. Any ideas??
Here is the current serial output:



Send me the modified R5.bin file and I'll look at it.
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10  Next Display posts from previous:    Page 7 of 10
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