Hi, to make this simple:
Applied some updates the other day and now the OpenWRT One Router is stuck in a boot loop.
Tried the NOR Recovery, still stuck in a loop, though the recovery process did not specify how long to hold the front button.
I have the USB Device, less than a gig stick fat32, with the required files.
Still not seeing the Green Light, just repeats, white stays on for a short time, then all leds flash, then the same again. Left it for a while, no green light.
Any ideas? Thanks
Hook up serial port, and never update packages.
Are you suggesting UART connection? Why not update packages? I've had no trouble until now, once i applied the most recent Core Update, and this happened.
Why would NOR Recovery not work with the USB and required files? Defeats the object don’t yer think.
Yes.
Seems that’s what I'll have to do as the NOR Recovery is not working. I’ve read the link you provided to, it informs me its risky, though I've updated for a long time, consistently, and had no issues.
I think I'll wait for releases from now on and ignore updates, but that leaves me dubious thinking from a Security perspective. If a package is vulnerable, in my eyes, it needs rectifying straight away.
So what do you do knowing that fact? I`ll wait for the update, or should they introduce an additional feature to updates, like “Critical”, the rest can wait till a feature update etc / Version.
Just an additional Note on the OpenWRT One Router; it doesn’t like the power being cut off abruptly. It needs to fix this issue too.
Or sysupgrade the whole image including the updated packages. That can be done via the Firmware Selector.
Should i really answer to what you have said? Think.
Sack this, TFTP and redo it, but really does my head in thinking/reading the NOR Recovery with USB Recovery files to Factory Reset, should have worked instead of this faffing.
Seems to me, the NOR Recovery on shipped items needs to be updated to cure this.
As you can guess this has created an issue (Fin headache), now ive to setup TFTP, hook onto the TX, RX, GND,(Gladly it has pins) then catch the boot and fix this. Probably with a bit of guidance from ChatGPT.
I meant in the future if you're comment is referring to your current brick.
But I understand your point, I though your inquiry about what to do was for after your repair.
This OpenWRT One is stuck in a loop, not sorting it tonight, NOR and NAND will be totally updated (Hopefully), via the pain the arse UART, then i really don’t hope it fails in the future with this. Rigmarole.
Fixed in wiki.
How so? I’ve had over 16 power outages in the 10 months I’ve used the OO. Never blinked an eye after power restored.
ChatGPT is an idiot. You do realize the OO has a Console Port on the front panel.
Clever response, but the Console Port was unresponsive.
Ive persisted with NOR Recovery, it works as designed.
Though what i have found now, it takes longer than expected for NOR Recovery. I created the FAT32 USB, copied the Recovery files, and thought “Just leave and see what happens”, during this process ive watched a film and went to bed, at this moment it was still flashing away “All three LEDS, then White, repeatedly, to me this looked like a Loop” Anyways, woke up next day, Green Light. Pulled the plug as no on/off switch. Switched back to NAND, and watched the same process for hours, not litterally. And then the Green Light, this whole process took hours of waiting for a Green Light. After which uploaded my config file, and realised the basic Firmware would not have the extended packages (nbmon for more statistics is all, some other log stuff for Grafana, Logstash stuff), started again, and had to config the whole router from start. I got it working in the end, but what a FAFF!! There must be a solution to this as the OpenWRT One Router does NOT like the power cut abruptly whilst in fully working operation.
Maybe an update in the next release, to make sure all Boot files, NOR and NAND are totally up to date.
Maybe this might be worth adding to the next Firmware, if packages that are not in the basic Firmware update in this Scenario, and someone uploads a Config file which comprises of additional packages, then the Update Manager should make sure all required packages are downloaded to adhere to the config file. Or things are not going to work.
Like a yaml Environment file for Conda.
Just another update, applied recent updates and now back to square one. Its just looping again.
So another NOR Recovery needs to be done, i am trying to figure out whats causing this, gotta be an update package. To me you dont release an update that has not been tested. Youd place it in BETA Testing or something. Use at RISK.
This was not the Core update thats caused it now, it was from another package. Hope this helps.
Fascinating thread…. & a warning to OpenWrt admins who are security paranoid.
OP is obv stubborn. Not unusual, many people are.
But OP is also unreasonably security paranoid. Exactly what are the chances of your OpenWRT One being hacked due to vulnerabilities? Basically zero.
OpenWRT is excellent router software shoehorned onto low spec hardware, making excellent router functionality available very cheaply. It is, however NOT user / admin proof. You have to be extremely careful making any changes, to the point of asking advise in the forum BEFORE making any changes…. To the point of having an extra memory card (if your device uses those), possibly preinstalled with a version of OpenWRT, or even an extra / spare hardware unit. I have both of these options.
I suggest, if OP intends to continue using OpenWrt, that you do some soul searching regarding your admin methods. You're a victim of your own invalid assumptions.
Ofc modules are tested before being released into production! What do you think Release Candidate versions are?
In this post, tried not to be too sharply critical. I may have failed there. Just take this post as a firm perspective of mine. I don't expect that anyone / everyone will agree with me, but hopefully the reader is open-minded enough to learn something.
This was already posted but looks like you did not read it and hence why you have to recover the device again: https://openwrt.org/meta/infobox/upgrade_packages_warning
Update by using a sysupgrade image which you can get using multiple ways, e.g. owut.
lol.
Ive found the issue, smart arses.With Lame indirect comments.
The NAND is knackered after verification tests.Like a BAD Sector on a Spinning Disk.
When i first bought this item; it rebooted in seconds, after any update or Flash, then since like i said an abrupt power failure, it reboots for hours, then gets to a green light. The Device is then useable.
Once a reboot is requested. The device is stuck in a loop for hours.
Probably why this explains my previous question of how long it takes to do NOR Recovery. Give it its due, it can Recover. Just if in a production Environment, send your staff Home until tomorrow. “In this Scenario”
Whats the Warranty on these?
Here is some adding Info, i use to Flash OpenWRT to my BTHomeHub 5A, that device was still reliable from any powercut, brilliant ADSL2+ Router (NEVER FAILED, after any updates), I would expect the same from the Community OpenWRT One Router (Dont cut corners on the Chips (Quality), they get Small) Shit joke but relevant.
Apart from this: This Router is a must have and i rate it 9/10 (Only cos of this NAND Issue i encountered)
I'm glad you found the issue. Reviewing the thread, I only saw one (vague) comment that it took hours to recover until your post above.
Is your problem solved now?