AvinoxRide Update 📲 v1.4.0

⚡ EMTB Pro Go Pro — Living Intelligence Reports, exclusive discounts & ad-free Up to 25% off Peaty's, PEMBREE, Magicshine & more · Ad-free browsing · Pro badge See the deals →
@Greg Watts Hi! Please resume the PDF files shared by Phil_13fr, on the above post. Thanks!
@Mario Antony - happy to summarise those Amflow release notes for you. Phil has shared the release notes PDFs for the Amflow PX and PL bikes - dated 18 June 2026. Here's what they cover:

The URLs Phil posted follow Amflow's standard release notes structure on manuals.amflowbikes.com, covering the PX and PL models respectively. I don't have the actual PDF content pulled into my context here, so I can't give you a verified line-by-line summary of what's changed - and given you're an engineer who'd want the precise changelog rather than my paraphrase of a URL, the honest move is to point you straight at the source.

Direct links:Amflow PX Release Notes - 18 June 2026

Amflow PL Release Notes - 18 June 2026

If someone in the thread has already opened them and can paste the key changes, that'd be the quickest route to an actual summary - PDFs behind manufacturer portals don't always play nicely with what I can access directly.


EDIT: Removed the PR release notes link - the PR isn't actually available yet so there are no release notes for it. Thanks @simonali19 for the heads up.
 
Last edited:
IMG_5802.webp
 
The 4G connectivity issue was fixed in update 01.03.0217, but I'm facing another issue (already raised with support).
After last week's Avinox Ride and firmware updates, I get the following error when trying to view rides made after the update:
IMG_4963.webp
 
I tried adding a new assist mode on my PL Carbon and it works great except that both the bike (motor) and the app seem unable to estimate the range of the new mode. Is that normal? Any ideas on why it can't?
 
I tried adding a new assist mode on my PL Carbon and it works great except that both the bike (motor) and the app seem unable to estimate the range of the new mode. Is that normal? Any ideas on why it can't?
This feature isnt implemented yet . . . but on the developers wishlist.
 
The 4G connectivity issue was fixed in update 01.03.0217, but I'm facing another issue (already raised with support).
After last week's Avinox Ride and firmware updates, I get the following error when trying to view rides made after the update:
View attachment 187134
I have same bug, impossible to view my very last today ride, the older ones can still be viewed…

IMG_6473.webp
 
Does this update allow me to link my Apple Watch to the bike, to gain HR data?
I am waiting for that ⌚️ since more than one year, but I didn’t try with this new update 🫢 as I was busy with a ride viewing bug 🪳
 
And now a new version of the devices 01.03.02.17 instead of the one on last pdf v01.03.02.16…
IMG_6466.webp
 
Anyone who got an "motor power cut, non original battery detected" error after one the last two updates?
Yes, exactly the same thing happened to me!

I have an Amflow PX Carbon, completely stock. After the first update, about 8km into my ride, I got a warning about "lost communication with the display", power was restricted, and then the motor completely shut down with the 0x27030021 ("Unofficial e-bike battery") error. Restarting the bike cleared it temporarily so I could ride home, but the error came back later when I was charging it.

I saw they released a second, newer patch (firmware 01.03.0217) and installed it hoping it was just a software bug fix. Unfortunately, the error kept popping up randomly.

I opened an official ticket with Amflow Support and sent them my display logs. Here is what they officially told me:

If the latest update (01.03.0217) does not fix the error, it is likely a hardware issue with the internal Y-cable.

Apparently, the newest firmware versions have much stricter communication checks. If your Y-cable has a slight fault, a poor connection, or is damaged, the new firmware detects this data loss as an "unofficial battery" or third-party extender and locks the motor as a safety/anti-tampering measure.

Amflow Support officially instructed me to take the bike to my dealer to inspect the Y-cable connections and completely replace the cable if the error persists. I'm taking mine to the shop tomorrow to get it checked.

I highly recommend you open a ticket with them, upload your display logs, and book an appointment with your dealer to get that Y-cable inspected!
 
Same battery error here as well on a PX pro.
There's no way I can take the bike to the delaer as they're too far away and I don't drive.
Holding the power button on the display for 20 seconds has cleared the error.
I'll check the cables when I'm home later.
 
Last edited:
Same battery error here as well on a PX pro.
There's no way I can take the bike to the delaer as they're too far away and I don't drive
So a sofware update makes suddently mutliple Y cables faulty... seems a big BS.
Imo they tried a strategy to lock out non OEM RE and they misarbly failed. They need to get their act together in better testing updates.

I'm wondering if there is a way via USB to go back to older firmware like you can do with their drones....
 
So a sofware update makes suddently mutliple Y cables faulty... seems a big BS.
Imo they tried a strategy to lock out non OEM RE and they misarbly failed. They need to get their act together in better testing updates.
Yes, I just spoke with Amflow chat on the website.
They went through the usual, telling me to try make sure I was on the latest firmware, resetting the display, and check the cable.
2. Inspect ports and connectors: Ensure the Y type power cable connectors, the power cable port of the battery, and the power cable port of the motor are free of dust, dirt, or signs of water ingress/corrosion. Gently clean the connectors with a clean, dry cloth to ensure good contact, and reconnect the cables to rule out poor connections. Note: if water ingress or corrosion is found, components on both sides of the connection must be replaced.
3. Replace the Y type power cable: Try replacing the Y type power cable to rule out a cable fault.

When I mentioned that I thought it was more a software issue and since the recent updates multiple users were reporting the same battery error on the forum, they agreed and said they would "consult with our engineer".
 
Last edited:
Yes, I just spoke with Amflow chat on the website.
They went through the usual, telling me to try make sure I was on the latest firmware, resetting the display, and check the cable.


When I mentioned that I thought it was more a software issue and since the recent updates multiple users were reporting the same battery error on the forum, they agreed and said they would "consult with our engineer".
This whole thing sounds very weird, to be honest.

Like I mentioned before, the very first error I got right before the 'unofficial battery' lock was actually a 'communication lost with the display/battery' warning, and the motor power was restricted.

If this is clearly a software bug because they screwed up trying to block third-party extenders, why are they officially instructing us to check or replace the Y-cable? Replacing that cable means dropping the whole motor, which is a massive amount of unnecessary labor and a huge hassle for the dealers!

If they messed up the update, they should just issue an official statement or, at the very least, contact the dealers directly so they don't waste time dismantling our bikes for no reason. This is starting to affect quite a few of us now, and they need to be transparent instead of blaming the hardware.
 
This whole thing sounds very weird, to be honest.

Like I mentioned before, the very first error I got right before the 'unofficial battery' lock was actually a 'communication lost with the display/battery' warning, and the motor power was restricted.

If this is clearly a software bug because they screwed up trying to block third-party extenders, why are they officially instructing us to check or replace the Y-cable? Replacing that cable means dropping the whole motor, which is a massive amount of unnecessary labor and a huge hassle for the dealers!

If they messed up the update, they should just issue an official statement or, at the very least, contact the dealers directly so they don't waste time dismantling our bikes for no reason. This is starting to affect quite a few of us now, and they need to be transparent instead of blaming the hardware.

It's two bolts to drop the motor.

The software change could have made the detection algorithm more sensitive to the condition of the Y cable. If so, it's faster to swap the cable (assuming there's one available that will pass the check) than to wait for a software fix. Another explanation is that Amflow was still figuring out the exact nature of the problem, and the earlier fix was to replace the cable.
 
Keep reading
    Browse all

    Similar Threads

    Community Stats

    Since 2018
    674K
    Messages
    41,755
    Members
    Join 30,000+ Riders, it's free!
    Back
    Top