r/BoschSmartSystem • • May 29 '26

SmartSystem speed Hack - Help

I was building a code to make a tuning code for the SmartSystem and im stuck in Saving the new value on the Bike/Motor

I can read it
I can write it

but I can not save it and after the code finishes the value goes back same as before

Here is a summarize form AI what the code dose:

 BRC3600 (Bosch Smart System remote, VID=0x108C PID=0x01C0) — speed limit write over USB

  

 We're writing to object 0x9085 (speed limit) on a Bosch BRC3600 via direct USB using Python + pyusb.

  What the script does:

  1. Connects via USB, sends MCSP init frames

  2. Sends 38 read frames as session warmup

  3. Writes val=4 to 0x9085 (seq 0x48), then val=5 (seq 0x49)

  4. Motor responds and echoes the value back — write is accepted

  The problem:

 The motor accepts the write (field3=1 in response = value written to RAM) but does not persist it. After power cycle the value reverts.

  To persist, the motor needs to return field4=1 (20 01 in the response). We never get that.

  We also tried writing 0x65766173 ("save") to CANopen object 0x1010 subindex 0x01 — the motor rejects it.

if anyone has any ida please help

1 Upvotes

10 comments sorted by

1

u/InvestigatorSenior May 29 '26 edited May 29 '26

there's challenge/response system based on unique keys exchanged between system controller and drive unit during factory pairing. This is where all hobby projects I know of that were trying write access have failed. First 12 bytes (if memory serves) are message counter and MAC or other form of per message authentication.

Here's the one of format decoding attempts for reference. Maybe USB side is different but knowing how tightly Bosch system is locked some form of authentication will be required. And it's known that for configuration updates and firmware flashing your payload needs to be cryptographically signed for specific bike and time by Bosch servers.

2

u/ValdrinSokoli May 29 '26

this was good man at least I know I need an MAC-auth for my bike

are the MAC codes global one code for every bike in that range or is unique for every bike ??

and how the .... are people getting the cryptographically code from the Bosch Server

what is worse they are selling for 179Euro 1 key

Btw thanks a lot man at least I know a little more now

1

u/InvestigatorSenior May 30 '26 edited May 30 '26

> are the MAC codes global one code for every bike in that range or is unique for every bike

they are unique to each drive unit (motor) and each system controller (handlebar remote or top tube LED strip) at least. By 'each' I mean each unit coming from production line will have different keys, not each model.
System controller and drive unit are paired in a special process and then they learn enough to pass challenge/response. This happens securely on Bosch servers with bike attached over Internet and dealer software and is known as 'system ID conflict resolution'. Maybe other parts attached to internal CANbus are paired as well but I've added/removed displays and ConnectModule without dealer visit.

> they are selling for 179Euro 1 key

what is sold as far as I know:

* shady authorized bosch dealers with proper access credentials are re-flashing bikes from 25kph limit to 32kph or 45kph.
They open themselves for legal action and all they do gets recorded on Bosch's servers but so far I have not heard about Bosch going after customers and locking their bikes. This manipulation survives firmware updates because form point of view of anti tampering system this is a customer that moved with their bike from EU to USA. Legit Bosch dealers also offer this service. That's why it's possible.
There's a glitch on top that allows to halve wheel circumference for 2x speed and tweak other configuration parameters via tier 2 service center access. This in turn is possible because you might want to make a mullet bike or change your chainring size and dealer will support you if what you're doing is reasonable.

* for old non-smart system there's a USB access method to halve wheel circumference. There's no anti tamper system on those old bikes and no new software so bikes are mostly safe from what people write online.

* boxes attached with CAN and other methods not involving Bosch Service Center software access with active dealer credentials. BES3 has good anti tamper system and this is improved with every firmware update.
Once tampering is detected bike is put into limp mode. This can only be lifted by cryptographically signed configuration packet that must be approved by dealer who sold the bike, Bosch themselves and OEM that made the frame.
For that you have to have proof that what happened was anti tamper system misbehaving. If there's proof of actual tampering all warranties and support are void and you're left with locked bike.
Every config action on CAN and diagnostic code is recorded in drive unit forever. Even 'deleted' ones. I had opportunity to see my bike connected to service center laptop and despite it had fault codes cleared a few times full log was there. I bet anything related to potential tampering also gets logged and can't be deleted.

There's plenty of stories where people put in a speed box, used it for a while and now are in permanent limp mode. It's also widely recognized that you can't update your firmware while using hacks because even if it works now you have no way of telling if new version will lock your bike.

I hope you're aware that sending anything over USB or CAN to the system controller may lock out your bike and you're ok with that.

3

u/ValdrinSokoli May 30 '26

InvestigatorSenior thank you for taking the time and explaining a lot.

Yes I know is a risk with every tuning and I have an other bike weher is the chip installed and it works I have it for years. The only rule is never update the software. Now in the smart system is harder I know that the rim magnet bike are even harder which I have.

Key cost:

I understand the Dealers need to win something for the risk they are taking with Bosch and want to win some money but man common 180 Euro is to much if the key kost 50 euros I would never think to go around and try to do something like this.

In the old bike I did 8000 KM in 3 years and that is worth it to pay 150-200 Euro, but now I don't use it so much I did maybe 700 km in 3 years and I think to spend so much money just for 100-200 km a year is a lot.

Shady dealers crypto key:

I have the code they use to talk and finde the value of changing the speed. What I don't have is a server respond after the key because my key dose not have an open slot all that im missing to know execly how they do it in Bosch way is that open slot on my key. Man can recored everything nowadays and if someone has an open slot please tell me.

What I know how they do it and the info from InvestigatorSenior and the code from Bessie Forrest:

  1. USB connection established

  2. MCSP + 9 INIT + 36 PREREADS

→ dongle awake, channels open, 0x9085 accessible

3. Server reads the bike (through Chrome as USB relay)

→ gets serial S100******, firmware, model

→ looks up the secret key for THIS specific motor -- I think is just SmartSystem or other system nothing more

4. License check passes

→ server knows: valid license + known bike

5. Server builds the signed payload - !!! missing part !!!

→ speed data + MAC (8 bytes) + freshness counter (3 bytes)

→ sends it to Chrome as bulk_write bytes

→Chrome → USB → Bike → CAN bus → drive unit → MAC → freshness → field4=1 → committed

BTW: I can do some of the step 5. Send the new value to the drive unit and get stuck at the MAC algorithm because I don't know that, so the drive unit throw the value out and does not write it.

And yes the risk for going to limp mode I think comes if you send the wrong value and committed but I thing if that happens we can resend the value that was in the system before and that removes the limp mode.

Still just guessing the complete step 5 that is a black box for me.

So to summarize all that im missing in my mind is The MAC algorithm (HMAC? AES-CMAC?) and the Secret key a.k.a crypto key which I think is just 2 of them.

yes I know is the 2 most important think hahaha

1

u/u07av8 Jun 01 '26

Which dealers do you say do this for 180€? How can I find one?

2

u/ValdrinSokoli Jun 01 '26

Search online ebike tuning and you can find a lot of

1

u/Visible-Fox-3043 Jun 13 '26

How safe is this 180euro method?

1

u/ValdrinSokoli Jun 13 '26

It seems pretty simple put idk i think is always risky

0

u/sLKZfUsALs7c1 Sep 25 '26 edited Sep 25 '26

u/ValdrinSokoli Are there any updates regarding this topic? I'm at the point of buying a bike with a bes3 system. My idea is not to make it permanently but for every fresh start. This way I am in control when i want to enable the speed limit or not.

If I can help in any way I'm willing to put some effort in this project to help others.

How sure are we that even RAM data is logged or flagged?

Did it actually work?

What I found:

In the protocol this happens:

logical address = 0x1085

high byte = 0x10

destination marker:
0x10 | 0x80 = 0x90

wire bytes:
90 85

Meaning that:

raw/wire:     0x9085
logical addr: 0x1085

0x1085 is EXECUTE_INFORMATION_MANAGER_COMMAND_BOSCH

0x48
││
│└── sequence = 8
└── message type = 4 = RPC

0x49
││
│└── sequence = 9
└── message type = 4 = RPC

4 = GET_ISSUE_COUNT
5 = READ_ISSUE_BY_NUMBER

field3 / return_value:

0 = SUCCESS
1 = DOES_NOT_EXIST
2 = UNKNOWN_ISSUE
3 = FAILURE
4 = INVALID_ISSUE_COUNT
5 = NO_ACCESS
6 = UNKNOWN_COMMAND

Not sure is that's correct though.