-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DQ381 FRF Full flash #135
Comments
These control units have a bug in their reflash process where block erase
and validate requests fail and need to be retried indefinitely. I haven’t
worked around this bug yet. Best to full flash with ODIS-E or VCP if you
need to change versions.
…On Tue, Jul 2, 2024 at 12:37 PM Eddy0697 ***@***.***> wrote:
Hello, flashing a calibration file for the dq381 works. but why doesn't
flashing a full FRF work? stays at block 3, 100% and then nothing happens
anymore. nothing was taken over
—
Reply to this email directly, view it on GitHub
<#135>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTO2LSBEBG4PUP2ODDUXDZKLXPNAVCNFSM6AAAAABKIDB7EKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DMOJQGI4DGMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Does this apply to the newest (post 2022) DQ381's? Is there any way that clutch pressure and shifting points can be set without actually having to decrypt/crack the TCU? |
Hello, flashing a calibration file for the dq381 works. but why doesn't flashing a full FRF work? stays at block 3, 100% and then nothing happens anymore. nothing was taken over
The text was updated successfully, but these errors were encountered: