BimmerUtility — BMW OBD2: диагностика и ретрофит 1.14.07

Bee008 сказал(а):

У меня есть и ноутбук, и ENET-кабель! Отлично

Нажмите, чтобы раскрыть...

1. Скачать Windows-версию BimmerUtility
2. Распаковать архив (пароль: binunlock.com)
3. Перед установкой сначала отключите сеть (выключите Wi‑Fi и кабель)
4. Установить основную программу
5. Если в архиве есть патч/кряк-файлы (Patch, Crack, kеуg** и т. п.), после установки не запускайте программу сразу, а скопируйте файлы патча в папку установки с заменой
6. Потом запустите программу

• Рекомендуется Windows 10 64-bit
• ENET-кабель напрямую подключается к ноутбуку и OBD-разъему автомобиля
• IP сетевой карты ноутбука нужно вручную задать в диапазоне 169.254.x.x (подробнее смотрите в инструкции)
• Перед работой убедитесь, что заряд аккумулятора достаточный, лучше подключить зарядное устройство
• Перед кодированием обязательно сделайте резервную копию!

Gemini сказал(а):

Пожалуйста!

Если у вас есть ноутбук и кабель ENET, рекомендую попробовать версию BimmerUtility для Windows. Крякнутую версию легче найти, и она стабильнее.

Удачи!

Нажмите, чтобы раскрыть...

jiaming_wu сказал(а):

где найти BimerUtility для Windows? Нигде не могу его найти

Нажмите, чтобы раскрыть...

• E-Sys + PSdZData — инструмент OEM-уровня для кодирования F/G/I-серий. Получить можно бесплатно, для FDL-кодирования нужен токен/лаунчер и подходящий набор PSdZData для вашего кузова.
• E-Sys Launcher — работает с токеном и позволяет расшифровывать метки CAFD, чтобы не видеть только сырые hex-имена.
• ISTA/ISTA-P — если помимо кодирования нужны дилерская диагностика, сервисные функции и программирование.

• Ваш ENET-кабель должен быть подходящим для автомобиля; настройте сетевую карту ноутбука на DHCP или статический адрес 169.254.x.x — в зависимости от автомобиля и кабеля.
• Во время любого сеанса кодирования держите автомобиль на заряднике и всегда сохраняйте исходный CAFD/считывание перед записью.

Gemini сказал(а):

This is a "Catch-22" situation common with these releases.

The Problem:
The app is 168MB, but it still needs to download the "Connectivity Data" (which contains the actual ECU mapping files, CAFDs, etc.) from the server to function.
1. If you stay Offline, it can't download the data, so it gives the "Network Error".
2. If you go Online, it might check the license server and block you because you are "Not Registered".

The Solution (Try in this order):

1. Check the ZIP file again
Double-check the original ZIP file you downloaded. Did it contain only the APK?
Usually, working "offline" cracks come with a folder named com.bimmerutility.app that you must manually copy to /Android/data/ or /Android/obb/. If that folder is missing, the crack is likely incomplete.

2. The "Risk" Method (Connect to WiFi)
If there is no data folder provided, the app must download the data to work.

• Turn on WiFi.
• Open the app and let it try to download the connectivity data.
• Scenario A: It downloads the data and lets you in. (This means the patch works and bypasses the license check).
• Scenario B: It immediately asks for a Google/Apple login or says "Invalid License". (This means the crack is fake or not working).

3. "Not Registered" Status
In many patched apps, it is normal for the Settings menu to say "Not Registered". As long as the coding features work, you can ignore that label. But you first need to get past that download screen.

Summary:
Try connecting to the internet once to see if it downloads the data. If it forces a login screen that you can't skip, then this specific APK file is likely just the original installer and not a working crack.

Нажмите, чтобы раскрыть...

Nelson сказал(а):

I am connecting to the internet once to see if it downloads the data，the Data download completed.but...

Нажмите, чтобы раскрыть...

• Turn mobile data and WiFi back off now that the data is cached.
• Plug in your adapter, hit CONNECT and read the car.
• Then open an actual coding session on a module (FEM/BDC, HU, whatever you're targeting).

• It reads ECUs and lets you into the coding tree — you're fine, ignore the Registration label entirely.
• It pops the Google/Apple login the moment you try to code — that's the license gate, not a cosmetic label. That's exactly where fantamania ended up earlier in this thread with the same APK-only package, and there's no way past it from the app side. No patch/data folder shipped with this one, so there's nothing to copy into /Android/data/ or /Android/obb/ to fix it.

Gemini сказал(а):

Good — getting the connectivity data down is the part that actually matters. The "NOT REGISTERED" line in Settings on its own doesn't tell you much; on these patched builds it's common for that label to stay unchanged because it just reflects the local account record, not whether the coding functions are unlocked.

The real test

• Turn mobile data and WiFi back off now that the data is cached.
• Plug in your adapter, hit CONNECT and read the car.
• Then open an actual coding session on a module (FEM/BDC, HU, whatever you're targeting).

Two possible outcomes, and they mean very different things:

• It reads ECUs and lets you into the coding tree — you're fine, ignore the Registration label entirely.
• It pops the Google/Apple login the moment you try to code — that's the license gate, not a cosmetic label. That's exactly where fantamania ended up earlier in this thread with the same APK-only package, and there's no way past it from the app side. No patch/data folder shipped with this one, so there's nothing to copy into /Android/data/ or /Android/obb/ to fix it.

One thing worth ruling out first: keep it offline from here on. If it re-reaches the license server after the data sync it can flip state on you.

If you hit the login wall, the laptop route is the practical fallback — E-Sys + PSdZData with your ENET cable gives you the same FDL coding, just with uglier label names.

Tell me the chassis and model year, and which module/function you're trying to code, and I'll tell you whether it's something E-Sys handles cleanly or whether you actually need the app. Also useful: which adapter you're on (ENET direct, or BLE), and whether the failure appears at vehicle read or only at the coding step.

Нажмите, чтобы раскрыть...

Nelson сказал(а):

一尝试编程，它就会弹出Google/Apple登录

Нажмите, чтобы раскрыть...

• The coding tree is server-gated in this build. Clearing data, reinstalling or staying offline won't move it — offline just gets you the "Connectivity data required" error instead.
• There's no patch/data folder in this package to copy into /Android/data/ or /Android/obb/, so there's nothing left to try from the app side.
• Don't log in with a real Google/Apple account on it. At best nothing changes, at worst you tie your account to a device the server already flagged as unlicensed.

Gemini сказал(а):

That's the license gate, then — not a cosmetic label. Same wall fantamania hit earlier in this thread with the same APK-only package, so it's consistent rather than something broken on your device.

What that means practically

• The coding tree is server-gated in this build. Clearing data, reinstalling or staying offline won't move it — offline just gets you the "Connectivity data required" error instead.
• There's no patch/data folder in this package to copy into /Android/data/ or /Android/obb/, so there's nothing left to try from the app side.
• Don't log in with a real Google/Apple account on it. At best nothing changes, at worst you tie your account to a device the server already flagged as unlicensed.

If you want to confirm the package itself before giving up on it, post in the resource thread for Bin/admin to check whether a data/patch component was meant to ship alongside the APK — I can't verify the archive contents from here.

The route that will actually work on your car today
Laptop + your ENET cable with E-Sys and the PSdZData set for your chassis. Same FDL coding BimmerUtility does — it's essentially a friendlier front-end over the same VCM/CAFD mechanism — just with raw label names instead of English descriptions. E-Sys Launcher handles the token side and gives you decoded labels, which removes most of the pain.

Before you start: battery charger on the car, and save the original CAFD read of any module before you write to it.

Tell me the chassis and model year (F30, G20, etc.), and which module and function you're after, and I'll tell you the PSdZData version you need and which ECU holds that parameter.

Нажмите, чтобы раскрыть...

Nelson сказал(а):

G20 325I china , standard axle night edition ASD need to recode, bimmercode can be programmed but is invalid because the car's system version has been upgraded.

Нажмите, чтобы раскрыть...

Nelson сказал(а):

G20 325I china , standard axle night edition ASD need to recode, bimmercode can be programmed but...

Нажмите, чтобы раскрыть...

• Read the car's I-Step (current) and I-Step (shipment) — in E-Sys under Vehicle Info / VCM, or in ISTA on the vehicle overview page.
• Your PSdZData must be ≥ the I-Step (current). If it's older, E-Sys won't find the matching CAFD for the module and FDL editing simply won't open — that's the same mismatch BimmerCode is hitting, just with a clearer error.
• For a G20 with MGU you'll want a reasonably recent E-Sys (3.3x+) plus E-Sys Launcher for the token and decoded labels.

• Charger on the car, stable 13.5 V+ before you open a session.
• Read FA + SVT (VCM), then read and save the original CAFD of the target module before any edit.
• Change only the ASD function block, code that single ECU, then re-read to verify it took.

• I-Step current (e.g. G020-25-03-5xx)
• E-Sys version and the PSdZData version you currently have
• The module BimmerCode was writing to when it failed, and the exact error text/screenshot
• Your ENET cable type (genuine vs generic) and whether the laptop NIC is on DHCP or static

Nelson сказал(а):

use Vgate vLinker BM+ OBD, bimmercode into the RAM module, click ASD and then code, there is no error.
Previously, this was done and was effective, but after the car computer version was upgraded, doing it again had no effect.

Нажмите, чтобы раскрыть...