# HereLink continuously ready for update but System up to date

**URL:** <https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829>\
**Category:** HereLink\
**Created:** [15 November 2021 07:31 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829 "2021-11-15T07:31:57Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![P1Herelink](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@P1Herelink](https://discuss.cubepilot.org/u/P1Herelink)\
**Post date:** [15 November 2021 07:31 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/1 "2021-11-15T07:31:57Z")

</div>

Hi,

My HereLink remote is showing System Updates window (after re-start) but after pressing the Check for update, it keep telling me that System up to date without any other option. I cannot proceed to any other window. The behavior is the same after lot of re-starts.  
Current version is BRU01210730

Any guidance will be appriciated.

Thank you.

---

<div class="post-metadata">

**Author:** ![Sven](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/sven/32/3367_2.png) [@Sven](https://discuss.cubepilot.org/u/Sven)\
**Post date:** [15 November 2021 08:34 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/2 "2021-11-15T08:34:30Z")

</div>

That version is the latest firmware.

You cannot use the Herelink unit?

---

<div class="post-metadata">

**Author:** ![P1Herelink](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@P1Herelink](https://discuss.cubepilot.org/u/P1Herelink)\
**Post date:** [15 November 2021 08:58 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/3 "2021-11-15T08:58:46Z")

</div>

I couldn’t use the remote at all however after playing around all available setup I found that home app was set by default to System Updates. I changed it to Herelink Launcher and now everything is working correctly. I’m not sure why the remote kept asking for update although it was updated without any option to continue however it’s working now so I’m fine.

Thank you for your respond.

---

<div class="post-metadata">

**Author:** ![Jai](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/j/5f9b8f/32.png) [@Jai](https://discuss.cubepilot.org/u/Jai)\
**Post date:** [5 August 2022 01:58 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/4 "2022-08-05T01:58:49Z")

</div>

did I understand wrongly? I am wondering why the updater rolls back the update.  
I believe the last six digits are the date of release in the version numbers FRU01 **220618** and BRU01 **211104**.

From the android system about the phone, I see BRU01211104.  
Can a developer enlighten me?

 ![fm](https://discuss.cubepilot.org/uploads/default/original/2X/7/7bba64096aaac3b82c631bc15b1c03fc64dab640.jpeg)

---

<div class="post-metadata">

**Author:** ![Michael\_Oborne](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/michael_oborne/32/13_2.png) [@Michael\_Oborne](https://discuss.cubepilot.org/u/Michael_Oborne)\
**Post date:** [5 August 2022 14:07 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/5 "2022-08-05T14:07:05Z")

</div>

please provide a adb bugreport.

---

<div class="post-metadata">

**Author:** ![Jai](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/j/5f9b8f/32.png) [@Jai](https://discuss.cubepilot.org/u/Jai)\
**Post date:** [6 August 2022 02:01 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/6 "2022-08-06T02:01:08Z")

</div>

[Steps correct](https://www.worldronemarket.com/herelink-manual/)?

So I am correct that the last six digits are the dates of the release and the updater roll back the latest version to previous version.

---

<div class="post-metadata">

**Author:** ![PickoTello](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/pickotello/32/4896_2.png) [@PickoTello](https://discuss.cubepilot.org/u/PickoTello)\
**Post date:** [7 August 2022 16:29 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/7 "2022-08-07T16:29:46Z")

</div>

Updated trough flashing tool  
I have the same issue. (or at least very similar issue)  
Current: FRU01220618  
Latest: BRU01211104

There are no applications - Solex, QGC etc on the current version.  
Not possible to change the home application (the only option is a system UPDATE )

When trying to update to the latest, the update doesn’t complete.  
At around 7% update stops downloading and start to verify the package and app goes into not responding state.

Help, that to do?  
why applications are missing?

---

<div class="post-metadata">

**Author:** ![PickoTello](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/pickotello/32/4896_2.png) [@PickoTello](https://discuss.cubepilot.org/u/PickoTello)\
**Post date:** [7 August 2022 18:59 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/8 "2022-08-07T18:59:22Z")

</div>

Update: It seems that I had an issue with 5.8ghz connection. On different router, it was possible to update Herelink to at least beta version.

---

<div class="post-metadata">

**Author:** ![Jai](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/j/5f9b8f/32.png) [@Jai](https://discuss.cubepilot.org/u/Jai)\
**Post date:** [8 August 2022 01:45 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/9 "2022-08-08T01:45:47Z")

</div>

> [@Michael\_Oborne](#):
>
> adb bugreport.

[attached](https://drive.google.com/file/d/1v6SjimzpN7L73zbTmHnV0HIDfyu114cB/view?usp=sharing).

---

<div class="post-metadata">

**Author:** ![Michael\_Oborne](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/michael_oborne/32/13_2.png) [@Michael\_Oborne](https://discuss.cubepilot.org/u/Michael_Oborne)\
**Post date:** [10 August 2022 09:19 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/10 "2022-08-10T09:19:32Z")

</div>

Current: FRU01220618 (factory image)  
Latest: BRU01211104

this is correct.

the factory image is newer than the Latest image, and is currently by design.

the factory image has no ability to link to an air unit, and is what ships on a brand new unit.

---

<div class="post-metadata">

**Author:** ![Jai](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/j/5f9b8f/32.png) [@Jai](https://discuss.cubepilot.org/u/Jai)\
**Post date:** [12 August 2022 03:47 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/12 "2022-08-12T03:47:48Z")

</div>

on second thought I cannot agree with it.  
other users may be able to buy the explanation. As a black box user, I cannot visualize it.

 ![1660275725311](https://discuss.cubepilot.org/uploads/default/original/2X/8/87bad1260f9a84bf2009bfe78a2d36c3bc335fde.jpeg)

---

<div class="post-metadata">

**Author:** ![Michael\_Oborne](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/michael_oborne/32/13_2.png) [@Michael\_Oborne](https://discuss.cubepilot.org/u/Michael_Oborne)\
**Post date:** [12 August 2022 08:11 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/13 "2022-08-12T08:11:37Z")

</div>

the factory image is newer than the stable release. agreed.  
stable is that, stable.  
factory is newer as there are more devices supported, which haven’t been pushed to stable yet.

we will soon push a new stable, once it has passed all the validation requirements, and at that point will likely be the same kernel

---

<div class="post-metadata">

**Author:** ![sibujacob](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/sibujacob/32/4663_2.png) [@sibujacob](https://discuss.cubepilot.org/u/sibujacob)\
**Post date:** [26 February 2023 11:09 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/14 "2023-02-26T11:09:02Z")

</div>

@Michael_Oborne

hi,

i am having the following udated version of Herelink. Could you please confirm if this is the latest update.

 ![Herelink version](https://discuss.cubepilot.org/uploads/default/original/2X/5/5fcb8806a45172fbb69dd3d032e0965ab97a3cdb.jpeg)

I had updated to the above version from the below version .

 ![Herelink previous version](https://discuss.cubepilot.org/uploads/default/original/2X/f/f705476a6b54ec7545a838f3c45458071959caa6.jpeg)

Also is the below the current QGC version

 ![QGC version](https://discuss.cubepilot.org/uploads/default/original/2X/4/4344730b853ba5b2d661f5b70b7e51936e622e47.jpeg)

---

<div class="post-metadata">

**Author:** ![Jai](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/j/5f9b8f/32.png) [@Jai](https://discuss.cubepilot.org/u/Jai)\
**Post date:** [29 March 2023 07:18 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/15 "2023-03-29T07:18:23Z")

</div>

8 months later, this version caused the ground unit to become useless and stuck at the system update app. I can’t go to the home screen to start QGC or Solex for example. the back key brings me to a black screen. the UI still prompts that an update is available which is an older version where **FRU01221123** is the latest version already installed. The update button should have been greyed and disabled.

I was forced to downgrade to BRU01211104 (old version kernel 4.9.27-264447) to get back the HereLink Launcher as the Home page. And I cannot pair it with the air unit (airunit-AAU01211129) anymore.

Is a very [expensive](https://www.3dxr.co.uk/autopilots-c2/the-cube-aka-pixhawk-2-1-c9/herelink-hd-video-transmission-c16/cubepilot-herelink-controller-unit-v1-1-p5224) piece of trash, and we have three sets. Ha. Skydroid even though is not perfect but did a much better job.

 ![IMG_20230329_151630](https://discuss.cubepilot.org/uploads/default/original/2X/2/2b9c6b45232ae7d2dd7cd35502370125bc3e8821.jpeg)

 ![IMG_20230329_153109](https://discuss.cubepilot.org/uploads/default/original/2X/0/026b231d734595135b37869aa6fe19deab871cf3.jpeg)

---

<div class="post-metadata">

**Author:** ![sibujacob](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/sibujacob/32/4663_2.png) [@sibujacob](https://discuss.cubepilot.org/u/sibujacob)\
**Post date:** [29 March 2023 07:56 UTC](https://discuss.cubepilot.org/t/herelink-continuously-ready-for-update-but-system-up-to-date/7829/16 "2023-03-29T07:56:13Z")

</div>

I can say that I do have a similar issue where the BRU was the latest version and the update done was with a RMU version just recently !! This is getting very weird…

First it came to this screen …

 ![Herelink update 2](https://discuss.cubepilot.org/uploads/default/original/2X/3/38ec2ded6578d66b64d8ebe8a33d00b34d9c442e.jpeg)

Then it came to the following screen update…

 ![Herelink update 1](https://discuss.cubepilot.org/uploads/default/original/2X/7/78459555a622db276592ef0d035d8619a743f61b.jpeg)
