OpenWRT One NAND mode bricked!

So I just got my new OpenWRT One hardware and have bricked it in record time trying to preform a sysupgrade. Could a very kind person please help me not only recover this device but actually get Luci installed and working (what I was trying to do in the first place)?

Ok, tell the filenames you used to program the device, and what is your device.

device is the OpenWRT One, file was openwrt-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb

Do you acquire IP address when connected to LAN port? Default snapshot image is bare-bones without luci.

I was able to ssh into yes, but I couldn't do much of anything... opkg update worked, but opkg install luci didn't. I then turned my attention to a full sysupgrade as I believed that would include luci (sidestepping this unknown error). However after I was finally able to scp the file over to /tmp I ran the command to start the sysupgade... got an error message, reboot and now the device won't do anything (in NAND mode, in NOR mode it still works but this is write protected I'm told).

In firmware selector add luci-mod-admin-full and luci-ssl , then sysupgrade.

Expand small arrow - customize installation, there in upper box add 2 packages.

At this point all I can do is set the physical switch to "NOR" and it will boot again, allowing me to ssh in once again.

I want to restore my NAND operation before continuing any further.

It is redundant to add luci-mod-admin-full and luci-ssl. The second one adds the first one.

@jassin000
NOR boot mode has a USB based recovery mechanism. Please follow the last paragraph in the following PDF.
Make sure the USB stick is formatted as FAT32 with MBR.

2 Likes

I received mine a little over 2 weeks ago, and OOB, LuCI came pre-installed. This was a bit of a surprise to me because Snapshot builds don’t come with the GUI by default. In retrospect, it made sense given this is a first in-house device by OpenWrt.

On first power on/boot with green led static, ssh root@192.168.1.1 confirmed the device was working.

From the wiki page I opened the link for Firmware OEM Stock URL that took me to the firmware-selector page. I noticed that LuCI was selected by default, and pointing my browser to 192.168.1.1 confirmed OOB w/LuCI.

A little late in your case (and recent other users it seems) so I’m just responding to advise others what to expect regarding OOB behaviour.

1 Like

I restored NAND operations following this section/instructions...

Full recovery

For when the unit does not boot anymore, there is a failsafe recovery method that can be used even if the ATF or bootloader are broken.

  • prepare a FAT32 formatted USB drive that contains the files:

    • openwrt-mediatek-filogic-openwrt_one-snand-preloader.bin

    • openwrt-mediatek-filogic-openwrt_one-factory.ubi

  • remove power

  • insert the USB drive

  • make sure NOR boot is selected

  • press and hold the button on the front side

  • power up the device

  • wait for the LED to go green

The NOR recovery system will then factory reflash the entire NAND flash.

1 Like

It just occurred to me this might also be the quickest/safest way to install an update.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.