OpenWrt

308 readers

1 users here now

OpenWrt news, tools, tips and discussion. Related projects, such as DD-WRT, Tomato and OpenSAN, are also on-topic.

Rules

Stay on topic: All posts should be related to OpenWrt and related projects, including DD-WRT, Tomato, OpenSAN, and more!
No offensive or low-effort content: Don't post offensive or unhelpful content. Be nice - keep it civil and friendly!
Describe images/videos, no memes: Please include a text description when sharing images or videos.
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English, behind a paywall or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy: Do not share links or direct people to pirated content.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No affiliate links: Posting affiliate links is not allowed.

founded 1 year ago

MODERATORS

ijeff@lemdro.id

inspector@gadgetro.id

I require assistance with fixing OKOD on a Linksys E8450 (sh.itjust.works)

submitted 5 months ago by Kalcifer@sh.itjust.works to c/openwrt@lemdro.id

0 comments fedilink hide all child comments

Unfortunately, a Linksys E8450 of mine has succumbed to the OKOD (OpenWRT Kiss of Death) (in case you are unfamiliar). From what I understand, it should be recoverable from it's current effectively bricked state. I've tried going through the process, but I haven't had too much luck, and I'm somewhat stuck at the moment, so I would appreciate some guidance. There's two potential objectives that I am hoping to acheive: the first, and primary, objective is to simply recover the router from its currently bricked state so that it can be used like normal, and secondly, if possible, recover the data, and configuration that was on it.

I have tried following this guide, but I'm not sure what I am supposed to do at the end. I completed the last step, but the router still isn't able to boot on its own. If I run boot from the U-Boot console, it appears to be able to boot into the OpenWRT CLI, but if I then reboot from that CLI, it shows the following error:

F0: 102B 0000
F6: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 0400 0041 [0000]
G0: 1190 0000
T0: 0000 02D7 [000F]
Jump to BL

NOTICE:  BL2: v2.9(release):OpenWrt v2023-07-24-00ac6db3-2 (mt7622-snand-1ddr)
NOTICE:  BL2: Built : 21:45:35, Oct  9 2023
NOTICE:  CPU: MT7622
NOTICE:  WDT: [40000000] Software reset (reboot)
NOTICE:  SPI-NAND: FM35Q1GA (128MB)
ERROR:   BL2: Failed to load image id 3 (-2)

That same error is what shows when I watch the serial output of the router while it boots from the power switch.

no comments (yet)

sorted by: hot top controversial new old

there doesn't seem to be anything here