[Important Info] k2.6 builds no longer support old devices

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2, 3  Next
Author Message
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11563
Location: Wherever the wind blows- North America

PostPosted: Fri Oct 08, 2010 14:56    Post subject: [Important Info] k2.6 builds no longer support old devices Reply with quote
Current k2.6 builds after ~16500 no longer support any old devices. This means that if you have a device that uses k2.4 then you must use k2.4 builds, and if you have a device that uses k2.6 then you must use k2.6 builds! There are no longer any devices that can run both.

If you accidentally flashed a newer k2.6 build on a device that needs a k2.4 build or vice versa then you must use either Serial or JTAG to recover it. See the Peacock Announcement for more details about recovering.


------more detailed info about the k2.6 build changes------

Thread Previously named:

CPU 4704 Owners (corerev=11) - No K26 builds after 15314 on the unit.
All other CPU's Corerev <16 - no K26 builds after 16500.


UPDATE It is now learned that any router with a corerev lower than 16 will no longer be supported with the K26 builds after ~16500. (per Eko)

It is advised that you test your unit's corerev BEFORE attempting to use the K26 builds on it.

The older corerev routers will still run the NEWD builds using the old wireless driver.

To test your corerev, login via telnet or ssh and run:

nvram get wl0_corerev

For dual radio devices, also run:

nvram get wl1_corerev

If the numbers are 16 or higher then you can use the K26 builds.


redhawk







Hi all,

After working with Eko to determine the problem...I found that the changeset of svn 15315 bricks the Asus WL-500W unit. This is only if you run K26-NEWD-2 builds...the regular V24 later builds work fine on the unit.

There have also been reports of bricks with the Asus WL-500gp. (although the 500gp is listed as unsupported in the K26 thread) http://www.dd-wrt.com/phpBB2/viewtopic.php?t=63757

So...to be on the safe side...those with these two models should not load any K26 build after 15314 unless you know how to use serial to debrick your asus.

[UPDATE] - originally this problem was found on the WL-500W unit. It has also been found on the WNDR3300, WL-500gP, and various other 4704 processor based units.

redhawk

_________________
The only stupid question....is the unasked one.


Last edited by redhawk0 on Mon Sep 22, 2014 15:37; edited 10 times in total
Sponsor
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11563
Location: Wherever the wind blows- North America

PostPosted: Fri Oct 08, 2010 17:40    Post subject: Reply with quote
OK...according to Eko...the newest Kernel does NOT support the 4704 devices any longer.

For 4704 units...use only V24 builds.

http://svn.dd-wrt.com:8000/dd-wrt/ticket/1768

redhawk

_________________
The only stupid question....is the unasked one.
AndreyPopov
DD-WRT User


Joined: 15 May 2008
Posts: 431

PostPosted: Sat Oct 09, 2010 16:42    Post subject: Reply with quote
so later - 05 oct BraynSlayer build brick my wl-500w.

may be not brick - it always in Firmware Restoration mode!
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11563
Location: Wherever the wind blows- North America

PostPosted: Sat Oct 09, 2010 21:40    Post subject: Reply with quote
AndreyPopov wrote:
so later - 05 oct BraynSlayer build brick my wl-500w.

may be not brick - it always in Firmware Restoration mode!



Manually put it in restoration mode...its not really in restoration mode after loading the 15315+ builds.

Then use the asus recovery tool to recover the router using the regular V24_mini_asus.trx file. (post 15315 builds will work fine for this)

Then load whatever V24 build you like.


[EDIT] a few more notes
My unit will sometimes restore using the 192.168.0.X subnet (my router indicates it is 192.168.0.49 in the serial output)....sometimes it is 192.168.1.X subnet. It all depends on if I've broken in to the CFE and issued an "nvram erase" command.

If your Asus Recovery tool goes to 99% and fails...you MUST use a serial cable to erase the current nvram partition.

redhawk

_________________
The only stupid question....is the unasked one.
AndreyPopov
DD-WRT User


Joined: 15 May 2008
Posts: 431

PostPosted: Mon Oct 11, 2010 12:17    Post subject: Reply with quote
but ping return TTL=100 like in restoration mode
and unit save it IP address - 192.168.1.2

now trying manualy enter to Restoration mode.
Z3r0
DD-WRT Novice


Joined: 03 Aug 2009
Posts: 16

PostPosted: Mon Oct 11, 2010 14:40    Post subject: Reply with quote
I bricked two WL-500Ws just now, then I read the forum!!!! I had to use the pin9 trick to recover. Got 1 working, second one is getting there Smile
AndreyPopov
DD-WRT User


Joined: 15 May 2008
Posts: 431

PostPosted: Mon Oct 11, 2010 16:33    Post subject: Reply with quote
redhawk0 wrote:
If your Asus Recovery tool goes to 99% and fails...you MUST use a serial cable to erase the current nvram partition.


I also see 99% and Fail. than I use wl500g-clear-nvram.trx and now router work!!!!!
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11563
Location: Wherever the wind blows- North America

PostPosted: Mon Oct 11, 2010 16:50    Post subject: Reply with quote
AndreyPopov wrote:
redhawk0 wrote:
If your Asus Recovery tool goes to 99% and fails...you MUST use a serial cable to erase the current nvram partition.


I also see 99% and Fail. than I use wl500g-clear-nvram.trx and now router work!!!!!


Ah...good to know...I've always used command line from CFE> prompt...thanx for the input.

redhawk

_________________
The only stupid question....is the unasked one.
pato
DD-WRT Novice


Joined: 20 Mar 2007
Posts: 32

PostPosted: Wed Dec 01, 2010 7:59    Post subject: Reply with quote
Just to clarify, this does not affect the Broadcom 4705 which is found in the WRT610N-v1?

Thanks,
pato
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11563
Location: Wherever the wind blows- North America

PostPosted: Wed Dec 01, 2010 12:35    Post subject: Reply with quote
pato wrote:
Just to clarify, this does not affect the Broadcom 4705 which is found in the WRT610N-v1?

Thanks,
pato


Correct...4705/4785 is a different beast...and is supported.

redhawk

_________________
The only stupid question....is the unasked one.
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11563
Location: Wherever the wind blows- North America

PostPosted: Mon Jan 03, 2011 23:06    Post subject: Reply with quote
If you've never had K26 running on the 500W before...it could be due to the CFE. Some of these 500W units required a CFE update in order to run K26.

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=393381#393381

redhawk

_________________
The only stupid question....is the unasked one.
mache
DD-WRT User


Joined: 11 Apr 2010
Posts: 311
Location: San Francisco Bay Area

PostPosted: Sat Feb 19, 2011 17:38    Post subject: Reply with quote
I have an Asus WL-500gp V2 running v24-sp2 (09/26/10) mega - build 15280M NEWD-2 Eko and would like to update the firmware.

Do folks think this will be fixed anytime soon or should I start shopping for a new router?

-- Mache
phuzi0n
DD-WRT Guru


Joined: 10 Oct 2006
Posts: 10141

PostPosted: Sat Feb 19, 2011 17:56    Post subject: Reply with quote
mache wrote:
I have an Asus WL-500gp V2 running v24-sp2 (09/26/10) mega - build 15280M NEWD-2 Eko and would like to update the firmware.

Do folks think this will be fixed anytime soon or should I start shopping for a new router?

-- Mache

k2.4 builds are not affected, only k2.6 builds no longer have support for BCM4704. Use the k2.4 builds as redhawk already said.

_________________
Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Shoreguy
DD-WRT User


Joined: 29 Jan 2009
Posts: 183
Location: Miami Beach

PostPosted: Tue Apr 12, 2011 1:22    Post subject: Reply with quote
Maybe a good time to update this sticky to include
corerev 12 (anything less than 16)
example: WRT310N v1 Broadcom BCM4785 chip rev 2 after:
EKO: 03-10-11 16403
BS: 03-17-11 16454

_________________
Home/Office
Miami Beach
Atlantic Broadband
Motorola SB6121

e4200v1
appleguru
DD-WRT Novice


Joined: 25 Apr 2009
Posts: 42

PostPosted: Wed Apr 13, 2011 19:55    Post subject: Reply with quote
Somehow I missed this thread.. just tried to flash my WNDR3300 with dd-wrt.v24-16785_NEWD-2_K2.6_openvpn_small.bin... Seems I've bricked it now. Any advice on un-bricking?
_________________
WNDR3300
FW: Eko 12268 mini-supp
Config: WL0: AP mode, WPA2 Personal, Mixed (bgn)
WL1: 802.1X client mode, 9dbi directional panel antenna soldered to board (right antenna)
Goto page 1, 2, 3  Next Display posts from previous:    Page 1 of 3
Post new topic   Reply to topic    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