Recovery from uboot is fairly simple

FYI on the reported inability to flash a new image from 4.4.22, 4.4.23 lede build. I have flashed r1727-4.4.23 with current kernel patch-set and I am unable to flash a new image. The /usr/sbin directory look thus:

     0 drwxr-xr-x    2 0        0              200 Sep 30 23:02 .
     0 drwxr-xr-x    5 0        0              100 Sep 30 23:02 ..
    20 -rwxr-xr-x    1 0        0            17660 Sep 30 23:02 ubiattach
    16 -rwxr-xr-x    1 0        0            13388 Sep 30 23:02 ubiblock
    16 -rwxr-xr-x    1 0        0            13448 Sep 30 23:02 ubidetach
    48 -rwxr-xr-x    1 0        0            46376 Sep 30 23:02 ubiformat
    24 -rwxr-xr-x    1 0        0            21772 Sep 30 23:02 ubimkvol
    20 -rwxr-xr-x    1 0        0            17540 Sep 30 23:02 ubirmvol
    20 -rwxr-xr-x    1 0        0            17560 Sep 30 23:02 ubirsvol
    20 -rwxr-xr-x    1 0        0            17484 Sep 30 23:02 ubiupdatevol

after an attempt. A reboot restores, but you cannot move forward, at least in that manner. Keep an older (i.e.4.4.21) image in your other partition if you do not have a serial console.

Edit: To the below data-point. I am moving forward from a r1655-4.4.21 build, perhaps my assumption regarding it being associated to the  kernel version is incorrect.

Edit2: I have opened FS#197

(Last edited by Villeneuve on 1 Oct 2016, 00:36)

@Villeneuve
@thelakesclub
I ran across the same thing 2-3-weeks ago I have to flash from a r16?? to upgrade (I thought it was only me)
I have not been able to flash from the new ver. If you try factory, sysupgrade, Linksys, they fail
And no reboot....But then scp asks for a password and luci is not accessible but ping and wan are still up and working.
A power down gets it working fine again.
It would be nice to not have to get my cable out of it's sealed bag.

Edit:Firmware Version LEDE Reboot r1656 / LuCI Master (git-16.266.66957-07591d7) Kernel Version4.4.22
I may have a kernel bump ahead of trunk. Could it be self inflicted?

Edit2: it sure has seemed longer... Build date Saturday, September 24, 2016, 5:49:24 PM
Hmm.....

(Last edited by northbound on 1 Oct 2016, 02:37)

I'm assuming this has been reported officially already?

Reading from a 2nd edit above.

Edit2: I have opened FS#197  <<< Thank you

(Last edited by davidc502 on 1 Oct 2016, 00:49)

So right now once we update to the latest trunk version, we can not upgrade anymore without a serial cable or booting from alternative kernel? That's a quite serious bug right there

Want to buy my v2?  Lol. I prefer my rt-ac68u.

Forgive my ignorance but what is a "FS#197"?

Some kind of reporting/ticketing system?

https://bugs.lede-project.org/index.php … ask_id=197

Will send you 50$ via paypal.  Just let me know where to send it.

Thanks northbound and anomeome.   For everyone else who may not know.  FS = Fly Spray

Is this considered a bug? Or should this be categorized as an enhancement request?

DFS is working correctly, however though the channel is changed, LuCi still shows channel 56, though radar was detected and it switched to 36.

[14859.614033] ieee80211 phy0: radar detected by firmware
[14860.217608] ieee80211 phy0: channel switch is done
[14860.222437] ieee80211 phy0: change: 0x40

Shouldn't LuCi now show channel 36 as the active channel?

Sorry but $50 is too low.
The 2.4ghz isn't as strong or fast as my rt-ac68u.
I haven't tried openwrt on it yet but it behaved the same way on dd-wrt and stock.
So I figure it's just my environment where Broadcom works better.

I'm assuming stock firmware would be the best, though lacking in features. I don't use anything but wifi and one lan pc.

(Last edited by Malachi on 1 Oct 2016, 14:36)

Try this i mage before you get rid of your WRT, I am running a V2 on it and extremely happy with it.

https://mega.nz/#F!7A0xFZJY!As3Zmj2fXNFa2QBaXPExKw

It is based on Openwrt, but is a full and complete image.
!st login password is "password" will prompt you to change it.

I will try it. Is it the "lede" build?

It is Openwrt.

It is a full and complete image, adblocking, "tor", everything.

Can I easily flash back to stock with out s serial setup?
I have the cable but would prefer to not open it up.
Btw, I don't need Tor or anything.

yep, just ssh in and :

fw_setenv boot_part 1(or 2)
reboot

Will boot back to alternate partition..

full image should be 14.9mb

Thanks for confirming. I thought I was the only one experiencing the problem. I had no problem with kernel 4.4.22. Whatever what was pushed to the master lede source in the last 48 hours or alittle bit more is what screwed me. Or was it kernel 4.4.23? Who knows.

I'm not sure if DFS is working correctly though.
On my WRT1900ACS with the lastest driver 10.3.0.18-20160823-1, DFS always detects radar after a while and switches.
See my report on https://github.com/kaloz/mwlwifi/issues/75.
For me only non DFS channels 36-48 are usuable.

At this page - wiki.openwrt.org/toh/linksys/wrt1x00ac_series - it shows the WRT1900ACSV2 as supported but the firmware download for the stable release does not indicate V2 and Linksys is all kinds of bent out of shape that V1 does not work on V2 hardware.

Because I'm a noob here, I'm not comfortable attempting to get approved to update the doc, but I don't even know what's right.  What I can confirm is that linksys' software on this thing kinda sucks.

Can anyone clarify/update?

Thanks in advance.

Wholly

@wholly, V2 info, I believe people have been flashing successfully.

Regarding the unable to move forward with flash issue, this is when I first came across the issue on the 28th. Make that the 27th, the post is the 28th.

(Last edited by Villeneuve on 1 Oct 2016, 18:12)

Thanks for the info!

Just sold on eBay. It was already listed with people watching it.

Have you tested this?

If this does work, you should be able to flip back-and-forth like using uboot tools in dd-wrt.

I've only done (tested) a serial call with 'run nandboot' or 'run altnandboot'