cancel
Showing results for 
Search instead for 
Did you mean: 

AP650 stuck on 10.0r8a and won't update to 10.1r5

AP650 stuck on 10.0r8a and won't update to 10.1r5

KevinP1
Contributor II

I have multiple AP650’s that are stuck on 10.0r8a and won’t update to the latest firmware of 10.1r5.  I’ve tried doing a firmware rollback, but didn’t have any luck. Any ideas?

1 ACCEPTED SOLUTION

KevinP1
Contributor II

Here’s the latest info from GTAC:

 

IQEngine 10.1r5 is not currently considered to be stable for the AP650. We will be removing it as the default firmware version for that model. The current recommended firmware for the AP650 is 10.0r8a.

 

I didn’t realize we would were beta testers a7fd520c0a254ed5b4803a92d20d9b08_1f609.png , but at least we all know to avoid 10.1r5 for the AP650.

View solution in original post

6 REPLIES 6

KevinP1
Contributor II

Hi Paul,

Here’s the output info:

Running image:      Current version

Current version:    HiveOS 10.0r8a build-242466
Build host:         cd102
Build time:         Fri May 29 06:39:45 UTC 2020
Build by:           build
Build cookie:       2005282339-242466

Backup version:     HiveOS 10.1r5
Build time:         Tue Jun  9 02:00:35 UTC 2020

Load after reboot:  Current version

Platform:           AP650
Bootloader ver:     v0.0.4.3
TPM ver:            v1.2.66.16
Uptime:             0 weeks, 0 days, 0 hours, 6 minutes, 30 seconds

 

2020-06-22 11:48:07 info    ah_image: system: write done: /dev/mtd6
2020-06-22 11:47:44 err     ah_bot: wifi: abort flash writing due to CPU overload or image upgrading
2020-06-22 11:47:44 info    ah_image: system: erase /dev/mtd6
2020-06-22 11:47:44 info    ah_image: system: write done: /dev/mtd4
2020-06-22 11:47:41 info    ah_image: system: erase /dev/mtd4
2020-06-22 11:47:41 info    ah_image: system: write done: /dev/mtd5
2020-06-22 11:47:41 info    ah_image: system: erase /dev/mtd5
2020-06-22 11:47:41 info    ah_image: system: write done: /dev/mtd0
2020-06-22 11:47:38 info    ah_image: system: erase /dev/mtd0
2020-06-22 11:00:27 info    ah_image: system: write done: /dev/mtd6
2020-06-22 11:00:04 info    ah_image: system: erase /dev/mtd6
2020-06-22 11:00:04 info    ah_image: system: write done: /dev/mtd4
2020-06-22 11:00:00 info    ah_image: system: erase /dev/mtd4
2020-06-22 11:00:00 info    ah_image: system: write done: /dev/mtd5
2020-06-22 11:00:00 info    ah_image: system: erase /dev/mtd5
2020-06-22 11:00:00 info    ah_image: system: write done: /dev/mtd0
2020-06-22 10:59:59 info    ah_image: system: erase /dev/mtd0

 

There was info for the show log buf | in image command.  

Even waiting 20 minutes it stays on the 10.0r8a image, and when I push the 10.1r5 it uploads, reboots, and as you can see it’s still keeping the 10.0r8a as the current image. I’ve tried the command “reboot backup” and doesn’t want to revert.

Paul_Wang
Extreme Employee

Does it keep same after waiting for 20 minutes? What do you mean by being stuck? Can you provide a screenshot?

What are the outputs of the following CLIs?

show version detail 

show log buf | in image

show log flash | in image

GTM-P2G8KFN