[OpenWrt-Devel] Cannot flash UBNT Loco M2

[Sven Roederer]

Hi,

for me it helped to go this way, to bring a NSM5 (xm) one member of our 
Freifunk-community bricked :
- UBoot was "1.1.4.2-s956 (Jun 10 2015 - 10:54:50)" and did not accept 
snapshot-images
- downgrading UBoot to "1.1.4.2-s594 (Dec  5 2012 - 15:23:07)" by flashing 
original xm5.5 image
- on uboot start the rescure tftp-server wit option -f (urescue -f), this also 
overwrites the uboot-code
-board boots up with AirOS5.5 and can be flashed to openWRT the normal way

found this hint to the "-f" option at the guys of the AREDN-project (http://
bloodhound.aredn.org/products/AREDN/wiki/HowTo/Unbrick)


I hope this help 
SVen

Am Friday 11 March 2016, 15:28:41 schrieb Matthias Schiffer:
> 
> Getting out of this state is not easy: you have a U-boot on your device
> that doesn't accept correct images, and an OpenWrt version that doesn't
> allow writing to the flash.
> 
> Through a serial console, you can try fixing the settings in U-boot; when I
> tried this the last time, I wasn't able to do so, but maybe I did something
> wrong. The U-boot console has a few interesting settings (I forgot the
> exact commands, but the "help" command should tell you everything you need
> to know):
> 
> * You can reset the MTD layout to the defaults. This makes the recovery
> accept correct images again. Unfortunately, in my experiments, this setting
> was not permanent even when I saves the environment after resetting the
> layout. In the hindsight, I remember there being a setting to disable flash
> protection, maybe that would made have the environment saving effective.
> 
> In the end, I fixed this by creating a patched OpenWrt image that allowed
> me to write to the uboot and uboot-env partitions; this allowed me to write
> back backups I had made of the uboot and uboot-env before I broke the flash
> layout by flashing OpenWrt. Obviously, this does not work if you don't have
> backups...
> 
> * If you don't plan to ever go back to AirOS again, it might be okay to
> just ignore the broken MTD layout in the U-boot settings. Get into the
> U-boot console, reset the MTD layout, start recovery, and flash an OpenWrt
> version after trunk r48829 or CC r48849.
> 
> 
> I hope this helps. I'd be interested if you find a way to parmanently reset
> the MTD layout from the U-boot console; unfortunately, I don't have a test
> device available at the moment.
> 
> Regards,
> Matthias
> 
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel