Posted: Wed Nov 15, 2017 23:58 Post subject: Re: Do keep up
hoot_spoot wrote:
Do keep up, watson.
We've already gone over that. Read the previous post. Telnetenable only works on windows 7. Not 10.
take an old flashdrive and create a bootable linux OS stick? go from there... _________________ n17tech blog
hw: r4500; WNDR4500v2; WNDR3700v2; WNR2000v3; WNR2000v5; BEFS841v3.1; WRT54GSv.4; WRT54G2v1.5; E900; E1000; E1200v2; WRT610Nv1; M20; RT-68P; DIR-601A1; DIR-615; DIR-635
Last edited by november17 on Thu Nov 30, 2017 18:18; edited 1 time in total
Posted: Thu Nov 23, 2017 3:01 Post subject: RE: Bricked WNDR4500V2??
I purchased a WNDR4500V2 used from ebay and I'm afraid I received a bricked device (was listed as working haha).
When the device is powered on all the lights illuminate for a brief 1/2 second, then just the power light is illuminated and it remains sold amber (the light corresponding to the RJ-45 port I am using is illuminated). I get one successful ping with ttl=100 and the rest are Network is Unreachable. After a few minutes, the router seems to try a restart or something as the lights all blink for a 1/2 second and then I'll get anywhere from 1 to 3 successful pings.
Also, if I hold down the reset button and power on the unit, I'll generally get a small moment where I can receive up to 5 successful pings with a ttl=100.
I have not been able to tftp the factory release to the device and have tried dozens of times hoping I can find the sweet spot, but the device seems to be active only for a few seconds at best, so I always get a transfer timeout of the tftp.
I've tried the many different options in the Peacock thread under section 6, with no luck. I'm not new to unbricking routers via tftp, so not a novice from that standpoint, but have not done a recover via a serial cable or such, although, I have done a successful pin short on a WNDR3400.
I'm wondering if anyone knows if this router can be recovered via serial cable or some other method??
Posted: Thu Nov 23, 2017 4:44 Post subject: Re: RE: Bricked WNDR4500V2??
camelriders wrote:
Also, if I hold down the reset button and power on the unit, I'll generally get a small moment where I can receive up to 5 successful pings with a ttl=100.
I have not been able to tftp the factory release to the device and have tried dozens of times
Google "wndr4500v2 serial pins"; looks like good results. Have you tried different OEM builds? _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Posted: Thu Nov 23, 2017 5:19 Post subject: Re: RE: Bricked WNDR4500V2??
jwh7 wrote:
camelriders wrote:
Also, if I hold down the reset button and power on the unit, I'll generally get a small moment where I can receive up to 5 successful pings with a ttl=100.
I have not been able to tftp the factory release to the device and have tried dozens of times
Google "wndr4500v2 serial pins"; looks like good results. Have you tried different OEM builds?
Yes, I have tried two OEM builds. I'll buy a cable and give it a shot.
I read the basic guides and now I wanna ask... What is the current recommended build/version for WNDR4500(v1)?
I probably must use 33525+ because of KRACK...
Does the latest version (33772) work fine with WNDR4500?
And, which version should I use for the initial flash? The Peacock thread suggests Blainslayer 14929 while the wiki page does 26138.
I read the basic guides and now I wanna ask... What is the current recommended build/version for WNDR4500(v1)?
I probably must use 33525+ because of KRACK...
Does the latest version (33772) work fine with WNDR4500?
And, which version should I use for the initial flash? The Peacock thread suggests Blainslayer 14929 while the wiki page does 26138.
The 'final' Broadcom krack fixes were in build 33678, and 33679 was missing many builds, so you want at least 33772. The Peacock doesn't indicate minimum builds to flash a particular device; that's in Supported Devices. So, you -definitely- don't want 14929. It is advised to follow the wiki for initial flash. I will be putting 33772 on my WNDR4500v2 and WNDR4000 today, as I have it on all my other DD devices atm. I will update this when I do; the v1 and v2 appear to have identical h/w specs except the latter has a BCM53125 switch (vs 53115).
Update: I have 33772 on my 4500v2 now, setup as a 2.4 GHz Client Bridge and 5 GHz Access Point, running fine. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
The 'final' Broadcom krack fixes were in build 33678, and 33679 was missing many builds, so you want at least 33772. The Peacock doesn't indicate minimum builds to flash a particular device; that's in Supported Devices. So, you -definitely- don't want 14929. It is advised to follow the wiki for initial flash. I will be putting 33772 on my WNDR4500v2 and WNDR4000 today, as I have it on all my other DD devices atm. I will update this when I do; the v1 and v2 appear to have identical h/w specs except the latter has a BCM53125 switch (vs 53115).
Update: I have 33772 on my 4500v2 now, setup as a 2.4 GHz Client Bridge and 5 GHz Access Point, running fine.
Thank you for your help. I'm gonna try 26138 for the initinal flash then 33772...
Posted: Thu Nov 30, 2017 20:52 Post subject: Re: RE: Bricked WNDR4500V2??
camelriders wrote:
jwh7 wrote:
camelriders wrote:
Also, if I hold down the reset button and power on the unit, I'll generally get a small moment where I can receive up to 5 successful pings with a ttl=100.
I have not been able to tftp the factory release to the device and have tried dozens of times
Google "wndr4500v2 serial pins"; looks like good results. Have you tried different OEM builds?
Yes, I have tried two OEM builds. I'll buy a cable and give it a shot.
Thanks for your help!
@jwh7, you were right, it's a good router - was able to recover back to a factory build with a serial cable that came in the mail today.
That being said, it's just like my WNDR4500v1 in that it won't take an initial DD-WRT build, although, the v1 never needed a serial cable to recover the device after a failed DD-WRT load.
Not sure it helps anyone, but this is what happens when it's trying to load the initial 26138 build (this is the tail end of the log):
found nvram
List of all partitions:
1f00 2048 mtdblock0 (driver?)
1f01 64 mtdblock1 (driver?)
1f02 32768 mtdblock2 (driver?)
1f03 97280 mtdblock3 (driver?)
1f04 32768 mtdblock4 (driver?)
1f05 98304 mtdblock5 (driver?)
1f06 64 mtdblock6 (driver?)
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
Rebooting in 3 seconds..Please stand by while rebooting the system...
I've also found the v2 router to be finicky about accepting firmware - make sure you're resetting the heck out of it then after you reset the heck out of it, reset the heck out of it again just to make sure. I have a v1 and v2 and they are really easy to el-bricko. Easy to recover with tftp but they do brick
This is pretty much how I feel every time I upgrade to a new DD-WRT build with these things _________________ n17tech blog
hw: r4500; WNDR4500v2; WNDR3700v2; WNR2000v3; WNR2000v5; BEFS841v3.1; WRT54GSv.4; WRT54G2v1.5; E900; E1000; E1200v2; WRT610Nv1; M20; RT-68P; DIR-601A1; DIR-615; DIR-635
Last edited by november17 on Fri Dec 01, 2017 6:01; edited 1 time in total
