ecuflash failed in the midle of a flash
Sep 2, 2007, 08:03 PM
#17
Iv'e been getting the same problem lately. Seems to be getting more and more frequent but I think its due to the 3year old battery aging. The voltage can appear good with a meter (12.6vdc) but when loaded may fizzle out.
Ive had the same error for several other problems too.
Try flashing with warm engine and laptop plugged intop garage
Ive had the same error for several other problems too.
Try flashing with warm engine and laptop plugged intop garage
Sep 3, 2007, 11:21 AM
#19
Newbie
Join Date: Jun 2007
Location: UAE, Abu Dhabi
Posts: 28
Likes: 0
Received 0 Likes
on
0 Posts
Iv'e been getting the same problem lately. Seems to be getting more and more frequent but I think its due to the 3year old battery aging. The voltage can appear good with a meter (12.6vdc) but when loaded may fizzle out.
Ive had the same error for several other problems too.
Try flashing with warm engine and laptop plugged intop garage
Ive had the same error for several other problems too.
Try flashing with warm engine and laptop plugged intop garage
Anyhow, I have to change my battery and give it a shot again, hopefully..
Sep 4, 2007, 09:44 PM
#26
Works now
Every time the problem happens it is fixed when I open ecuflash from a different location.
First time I was using the desktop icon it was fixed immedialy by opening from start menu. This time it was fixed by opening from the .exe in programfiles.
Anyone know why? I'm talking a dozzen unsuccessful attempts then suddenly opening from different icon fixes it.
This all started after a short trial of that crappy 1.31 that I have uninstalled back when this first started
Every time the problem happens it is fixed when I open ecuflash from a different location.
First time I was using the desktop icon it was fixed immedialy by opening from start menu. This time it was fixed by opening from the .exe in programfiles.
Anyone know why? I'm talking a dozzen unsuccessful attempts then suddenly opening from different icon fixes it.
This all started after a short trial of that crappy 1.31 that I have uninstalled back when this first started
Sep 7, 2007, 06:27 AM
#27
Newbie
Join Date: Jun 2007
Location: UAE, Abu Dhabi
Posts: 28
Likes: 0
Received 0 Likes
on
0 Posts
Works now
Every time the problem happens it is fixed when I open ecuflash from a different location.
First time I was using the desktop icon it was fixed immedialy by opening from start menu. This time it was fixed by opening from the .exe in programfiles.
Anyone know why? I'm talking a dozzen unsuccessful attempts then suddenly opening from different icon fixes it.
This all started after a short trial of that crappy 1.31 that I have uninstalled back when this first started
Every time the problem happens it is fixed when I open ecuflash from a different location.
First time I was using the desktop icon it was fixed immedialy by opening from start menu. This time it was fixed by opening from the .exe in programfiles.
Anyone know why? I'm talking a dozzen unsuccessful attempts then suddenly opening from different icon fixes it.
This all started after a short trial of that crappy 1.31 that I have uninstalled back when this first started
I've changed the battery and tried but still same error!
then I've checked all fuses and we found out all fuses were good!
Last thing is wiring issue, now i have to check the ODBII wires "white pulg" too!
Question: what is the "White Plug" function, is it power?
Good luck guys and wish me too...
Sep 7, 2007, 07:30 PM
#29
It is NOT just a ground.. Its the wire that lets the ECU know you want to flash it. (bootstrap pin) the voltage from your USB port, and the 12v from your car is combined to provide around 15-17v. This is why if you have low battery voltage, or are powering your laptop from the car, the combined voltage may not be enough to trigger the bootstrap.
A typical problem would be an error "no response to any known code"
If you have a bad flash, there may not be enough code for it to boot on its own, so it won't recognize the default init code. The unlocker tool, when run at the same time as ECUFlash, adds another code to the attempt, this code triggers a hard coded bootstrap routine or recovery bootstrap.
This is why these questions are being asked.
A typical problem would be an error "no response to any known code"
If you have a bad flash, there may not be enough code for it to boot on its own, so it won't recognize the default init code. The unlocker tool, when run at the same time as ECUFlash, adds another code to the attempt, this code triggers a hard coded bootstrap routine or recovery bootstrap.
This is why these questions are being asked.