-
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
Flashing stopped working after 3 or 4 successes, hangs/aborts at "Upgrading to programming session..." #139
Comments
Hi; I can’t see this Google Drive link. Usually this means you flashed a
file without a matching power class, but it could have a less fatal cause
too.
…On Sun, Jul 21, 2024 at 4:45 PM jbhebert77 ***@***.***> wrote:
Was able to unlock and successfully flash the ECU 3 or 4 times, but now
when I try to flash it with either a tune or stock file, it gets to
"Upgrading to programming session..." and aborts. If I try to relock, I get
the same error. If I try to unlock again, I get an error unpacking the
file. "Get ECU Info" still works. I suspect I did something I shouldn't
have and bricked the ECU, but I want to know if there is any way to recover.
Logfiles too large to attach; archived here instead:
https://drive.google.com/drive/folders/1qJGLlSsSWACjGYETGZLhUOs9gCTjNi9B?usp=drive_link
—
Reply to this email directly, view it on GitHub
<#139>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTO2KVU4YXCVEU3HUGJBLZNQMWFAVCNFSM6AAAAABLHEY5E2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDCNJZGQ3TGMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
My apologies, permissions have been updated. It was a Hail Mary pass at an attempt to get a CTUA block running with a CXCA ECM and sensors, so it wouldn't surprise me if that is the case. Thank you for your time. |
did you solve this issue? |
Was able to unlock and successfully flash the ECU 3 or 4 times, but now when I try to flash it with either a tune or stock file, it gets to "Upgrading to programming session..." and aborts. If I try to relock, I get the same error. If I try to unlock again, I get an error unpacking the file. "Get ECU Info" still works. I suspect I did something I shouldn't have and bricked the ECU, but I want to know if there is any way to recover.
Logfiles too large to attach; archived here instead:
https://drive.google.com/drive/folders/1qJGLlSsSWACjGYETGZLhUOs9gCTjNi9B?usp=drive_link
The text was updated successfully, but these errors were encountered: