Dodgy settings/attempted hack?

[Lost]

It's not too surprising you'd see notifications in Chinese as most of the internal services on the phone would be managed by Emdoor. It's unlikely Stark would know much more than that.


1.2.8 is the latest and unless Stark is maybe implying you have a corrupt firmware version there wouldn't be a way to update (and obviously 0.0.0 is nonsense so it seems more likely whoever your talking to at Stark is clueless).

It wouldn't be surprising if this had happened before or immediately after an update, but I've had the bike 7 months now, riding most days. Last Friday was the first time it happened, and has happened multiple times since.

It's possible that they are implying corruption, although the bike is working perfectly.

It's also VERY possible that the CSR has no idea what they are doing... I discovered that lovely nugget of information when I asked a question, and got 4 different answers (no exaggeration).

 

[Chaconne]

It seems that it could be more serious...

I emailed "support" with a picture of the issue and an explanation of what was happening.
Got a message back saying they tried to remote in but bikes firmware was out of date, and to update.

Checked my bike and it's at 1.2.8. Went through the steps to update anyway, but no update found....

Messaged back explaining this, and was told to try updating again as they tried remoting in again and the was bike was showing update 0.0.0. (Wouldn't that be a bricked bike?)

Took a picture of the update to confirm to them and straight up asked if this is a data breach?

It's been total radio silence from them since. Even after repeated requests for updates. Even offering to bring the bike straight to the factory. Nothing.

As a result I'd suggest anyone who's getting this message to contact Stark.

Usually there are two copies of firmware (I am assuming you are talking about the bike firmware). One which is loaded and one (or more) that is saved. Typically a saved copy is updated. So your bike should always work. If there is something wrong with the phone and it is not getting the right data or if an update failed then you might get the results you see. The "loaded" copy of the firmware is usually never live updated in any embedded system I have ever worked on and your bike should be fine with the loaded copy and not be bricked. The version check should disallow a 0.0.0 load if that is in a stored area.

It doesn't sound like a data breach. More like somebody at Customer Support doesn't know what they are looking at.

 

[Chaconne]

It's possible that they are implying corruption, although the bike is working perfectly.

It's also VERY possible that the CSR has no idea what they are doing... I discovered that lovely nugget of information when I asked a question, and got 4 different answers (no exaggeration).

This

BTW they may have "pushed" a firmware update and they are looking at the stored area and see 0.0.0. But your bike wouldn't be able to use that.

 

[Lost]

This

BTW they may have "pushed" a firmware update and they are looking at the stored area and see 0.0.0. But your bike wouldn't be able to use that.

that's the thing, last update was July for all of us. Can't understand why this is an issue now?

Why are others noticing the same in resent weeks?

Why 0.0.0, when bike was delivered at 1.something?

 

[Chaconne]

that's the thing, last update was July for all of us. Can't understand why this is an issue now?

Why are others noticing the same in resent weeks?

Why 0.0.0, when bike was delivered at 1.something?

My hunch is whoever was looking at your "version" didn't know what they were looking at. As long as your bike is working fine and you see 1.2.8 and that is current you should be good. I wouldn't mess with firmware anymore if I were you until a general update for everyone comes out. Or the CS person can make a real case for it.

It surprises me that they are trying to debug your firmware in any case. Maybe I lost the idea of this thread but wasn't the issue that some icon was showing up on the phone app (like a Waze thing or something)? Seems like they should be debugging with their phone provider(s) not making customers update firmware...