Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Joe Touch <touch@isi.edu>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Fri, 10 Jul 2015 00:22:10 -0700	[thread overview]
Message-ID: <259D837E-4664-4756-843E-F0AF379F50B8@isi.edu> (raw)
In-Reply-To: <alpine.DEB.2.02.1507100900171.11810@uplift.swm.pp.se>



> On Jul 10, 2015, at 12:03 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
>> On Tue, 7 Jul 2015, Joe Touch wrote:
>> 
>> Some questions:
>> 
>>> On 7/6/2015 11:16 PM, Mikael Abrahamsson wrote:
>>> ...
>>> You can flash back the factory firmware without serial, you just use
>>> sysupgrade with the Linksys factory image.
>> 
>> How does that differ from mtd, e.g., as indicated here (which doesn't
>> mention sysinstall)?:
>> http://wiki.openwrt.org/doc/howto/generic.uninstall
> 
> http://wiki.openwrt.org/toh/linksys/wrt1200ac#how_to_flash_the_firmware_to_device
> 
> "Revert to Linksys Stock Firmware"
> 
> So you can either use the web ui or the "sysupgrade" command to go back to Stock firmware.

I see the word "sysupgrade" only her, but that is in reference to the img type not the command :

----
When flashing from OpenWrt, use the "sysupgrade" image. Although the factory image will work, the sysupgrade image has the fringe benefit of preserving the UBI container between flashes, which provides some wear-leveling.
----

Can you explain where the info on using the sysupgrade command to revert to the factory image is??

> 
> I have only used the mtd method once, and that was when there was a problem with the flash for some reason and I was recommended that method instead by an OpenWrt developer.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2015-07-10  7:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  1:02 Joe Touch
2015-07-07  2:23 ` Rich Brown
2015-07-07  4:22   ` Joe Touch
2015-07-07  7:20     ` Sebastian Moeller
2015-07-07 12:03       ` [Cerowrt-devel] [Bloat] " Kevin Darbyshire-Bryant
2015-07-07 14:07     ` [Cerowrt-devel] " Rich Brown
2015-07-07 18:19       ` Matt Taggart
2015-07-08  1:54         ` Rich Brown
2015-07-08 18:37         ` Joe Touch
2015-07-08 20:15           ` Sebastian Moeller
2015-07-08 20:28             ` Joe Touch
2015-07-08 22:16               ` Sebastian Moeller
2015-07-09  1:34                 ` Rich Brown
2015-07-08  0:48   ` Jim Reisert AD1C
2015-07-08  2:47     ` Dave Taht
2015-07-07  6:16 ` Mikael Abrahamsson
2015-07-07 18:34   ` Joe Touch
2015-07-10  7:03     ` Mikael Abrahamsson
2015-07-10  7:22       ` Joe Touch [this message]
2015-07-10  7:48         ` Mikael Abrahamsson
2015-07-10  8:01         ` Sebastian Moeller
2015-07-10 16:57           ` Joe Touch
2015-07-07 15:40 ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=259D837E-4664-4756-843E-F0AF379F50B8@isi.edu \
    --to=touch@isi.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox