Problems updating form ZA1JA01G to ZA1JD00G ROM - fixed disable U0155 code in rom - Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community

steve99 · 08-27-2014, 12:02 AM

Problem now fixed by disabling CEL code U0155 in rom you will need the latesd definition files as the option was not availablein original definitions for romraider or ecuflash.

Ok My car was originally ZA1JA01G (2013) all ok no problems, flashed the latest STOCK ZA1JD00G rom absolutely stock nothing changed. Flashed with Tactrix/Ecuflash. (I also have OFT but it will not jump calid's without a bit of messing around)

Got CEL light Code U0155 Can Buss communications erro,r thought no worries get that occasionally after flash or when plugging in logging device or OFT. Tried to clear code no go comes straight back.

Car Starts ok idles runs ok up to about 4000 rpm then no power (this is on completely stock ZA1JD00G rom. Stop reset clear code comes straight back. Logged and everthing looks pretty normal , suspect its in limp home mode due can- buss error.

Flash back stock ZA1JA01G rom all sweet no codes no light car runs fine no can-buss problems.

Appears something has changed with new 2015 cars either software in another computer or some hardware that is not installed in earlier cars and ECU code is not talking to something correctly on can-buss.

anyone else flashed a D00G rom to an earlier model car with success ?

@Shiv@Openflash @Td-d any ideas

AP756 · 08-27-2014, 03:06 AM

Tried to flash ZA1JD00G on my European GT86 to no avail. Due to limited time I just stopped... => no success, no big help.

Can bus communication error can be "produced" anytime very easily: Just plugin any hardware which tries to communicate with the ECU as long as the startup routines are not finished. Eg. plugin a mobile running Torque, stop engine for about 2 mins (ECU goes to sleep), then restart and you get that communication error.

Did you try to reset the code while running the engine? If not please try. It works for me every time I forget to stop Torque while refuelling the car... (still running ZA1JA01G)

So I assume they changed some code in startup and this is a timing problem. To be sure you might try to flash D00G again, you will get the failure code, you have to reset the code (no problem to do so with Torque) while engine runs. Failure gone means I'm correct with startup routines, failure comes back immediately you're right, it's a hardware problem, something changed.

Bye for now Fred

steve99 · 08-27-2014, 04:13 AM

Quote:

Originally Posted by AP756

Tried to flash ZA1JD00G on my European GT86 to no avail. Due to limited time I just stopped... => no success, no big help.

Can bus communication error can be "produced" anytime very easily: Just plugin any hardware which tries to communicate with the ECU as long as the startup routines are not finished. Eg. plugin a mobile running Torque, stop engine for about 2 mins (ECU goes to sleep), then restart and you get that communication error.

Did you try to reset the code while running the engine? If not please try. It works for me every time I forget to stop Torque while refuelling the car... (still running ZA1JA01G)

So I assume they changed some code in startup and this is a timing problem. To be sure you might try to flash D00G again, you will get the failure code, you have to reset the code (no problem to do so with Torque) while engine runs. Failure gone means I'm correct with startup routines, failure comes back immediately you're right, it's a hardware problem, something changed.

Bye for now Fred

Thankyou

If your trying to flash D00G with tactrix/ecuflash make sure you get the updated definition for ecuflash as the original D00G def had the incorrect flashing mode set, latest one is corrected but only corrected a few days ago.

will try again and try reseting code with engine on in case it needs comms active to reset

AP756 · 08-27-2014, 04:56 AM

Hi Steve, due to lack of time I have to wait... Next month I have an inspection, I'll ask my dealer to update officially ;-). Or someone comes around with an OFT flashable solution... (Shiv?)

Bye for now Fred

steve99 · 08-27-2014, 06:44 AM

Quote:

Originally Posted by AP756

Hi Steve, due to lack of time I have to wait... Next month I have an inspection, I'll ask my dealer to update officially ;-). Or someone comes around with an OFT flashable solution... (Shiv?)

Bye for now Fred

OFT will not let you update from A01G to D00G as it wants to match calid.

Td-d · 08-27-2014, 10:39 AM

Hi Steve - sounds like it's put the car into limp mode - I assume you flashed with ignition in the on position, and no interruptions (door opening, plug in devices, etc.)? I would be surprised if there was a fundamental change in the start-up code.

ML · 08-27-2014, 03:57 PM

did you edit the d00g rom in romraider?

steve99 · 08-27-2014, 04:14 PM

Quote:

Originally Posted by ML

did you edit the d00g rom in romraider?

no editing at all was absoutly stock rom

steve99 · 08-27-2014, 04:15 PM

Quote:

Originally Posted by Td-d

Hi Steve - sounds like it's put the car into limp mode - I assume you flashed with ignition in the on position, and no interruptions (door opening, plug in devices, etc.)? I would be surprised if there was a fundamental change in the start-up code.

my thoughts as well , will give it another go soon when i get some spare time

ML · 08-27-2014, 04:20 PM

I had a similar issue once where it would keep putting the car into limp mode after I loaded a new rom. Unhooking the battery and putting it back on seemed to fix it for me.

ML · 08-27-2014, 09:52 PM

So I guess you got it working

steve99 · 08-27-2014, 10:11 PM

Quote:

Originally Posted by ML

So I guess you got it working

have not tried again, once I get wife out of car long enough will have another go in next day or two

steve99 · 08-28-2014, 04:34 AM

OK I think I found the problem.

Looks like a possible error in the definitions for ZA1JD00G ROM for ECUFLASH the checksum module is blank for D00G rom when looking in ECUFLASH ROM info
on the A01G ROM its set to "subarudbw"

A01G roms flash ok
D00G roms either fail on checksum module at end or flash ok and get CANBUSS error car in limp home mode.

On non checksum corrected ROM get error at end of flash checksum module fail

On checksum corrected ROMS it flashes ok but get CANBUSS error and limp home mode.

On an A01G ROM Checksum Module : subarudbw

on D00G ROM Checksum Module : (nothing it's blank)

@Td-d am I on the right track here ??

Td-d · 08-28-2014, 06:28 AM

I think that's if - did not come through when I ran the script on the RR definition to convert to Ecuflash. I've edited and uploaded to Github.

08-27-2014, 12:02 AM	#1
steve99 Banned Join Date: Dec 2013 Drives: FT86 Location: Australia Posts: 7,996 Thanks: 1,035 Thanked 4,992 Times in 2,983 Posts Mentioned: 598 Post(s) Tagged: 2 Thread(s)	Problems updating form ZA1JA01G to ZA1JD00G ROM - fixed disable U0155 code in rom Problem now fixed by disabling CEL code U0155 in rom you will need the latesd definition files as the option was not availablein original definitions for romraider or ecuflash. Ok My car was originally ZA1JA01G (2013) all ok no problems, flashed the latest STOCK ZA1JD00G rom absolutely stock nothing changed. Flashed with Tactrix/Ecuflash. (I also have OFT but it will not jump calid's without a bit of messing around) Got CEL light Code U0155 Can Buss communications erro,r thought no worries get that occasionally after flash or when plugging in logging device or OFT. Tried to clear code no go comes straight back. Car Starts ok idles runs ok up to about 4000 rpm then no power (this is on completely stock ZA1JD00G rom. Stop reset clear code comes straight back. Logged and everthing looks pretty normal , suspect its in limp home mode due can- buss error. Flash back stock ZA1JA01G rom all sweet no codes no light car runs fine no can-buss problems. Appears something has changed with new 2015 cars either software in another computer or some hardware that is not installed in earlier cars and ECU code is not talking to something correctly on can-buss. anyone else flashed a D00G rom to an earlier model car with success ? @Shiv@Openflash @Td-d any ideas Last edited by steve99; 09-02-2014 at 08:42 PM.

08-27-2014, 04:56 AM	#4
AP756 Member Join Date: Jun 2014 Drives: GT86 Toyota Location: Germany Posts: 22 Thanks: 7 Thanked 9 Times in 5 Posts Mentioned: 1 Post(s) Tagged: 0 Thread(s)	Hi Steve, due to lack of time I have to wait... Next month I have an inspection, I'll ask my dealer to update officially ;-). Or someone comes around with an OFT flashable solution... (Shiv?) Bye for now Fred Last edited by AP756; 08-27-2014 at 05:58 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
>>> 3 New Lightweight Flow Form Wheels <<< 720 FORM Compilation	Anorexic 86	Wheels \| Tires \| Spacers \| Hub -- Sponsored by The Tire Rack	346	06-11-2019 08:27 PM
access path denied when updating OFT	dejxx	Software Tuning	2	06-24-2014 08:09 PM
Problem with updating Pioneer AVH-X8450BT	iam86	Electronics \| Audio \| NAV \| Infotainment	0	06-25-2013 04:17 AM
Issue updating Registry.	IloveBaldEagles	Site Announcements / Questions / Issues	1	03-18-2013 08:19 PM
Scion.ca down - updating?	Sport-Tech	CANADA	8	04-05-2012 04:00 PM

08-27-2014, 03:06 AM	#2
AP756 Member Join Date: Jun 2014 Drives: GT86 Toyota Location: Germany Posts: 22 Thanks: 7 Thanked 9 Times in 5 Posts Mentioned: 1 Post(s) Tagged: 0 Thread(s)	Tried to flash ZA1JD00G on my European GT86 to no avail. Due to limited time I just stopped... => no success, no big help. Can bus communication error can be "produced" anytime very easily: Just plugin any hardware which tries to communicate with the ECU as long as the startup routines are not finished. Eg. plugin a mobile running Torque, stop engine for about 2 mins (ECU goes to sleep), then restart and you get that communication error. Did you try to reset the code while running the engine? If not please try. It works for me every time I forget to stop Torque while refuelling the car... (still running ZA1JA01G) So I assume they changed some code in startup and this is a timing problem. To be sure you might try to flash D00G again, you will get the failure code, you have to reset the code (no problem to do so with Torque) while engine runs. Failure gone means I'm correct with startup routines, failure comes back immediately you're right, it's a hardware problem, something changed. Bye for now Fred

08-27-2014, 10:39 AM	#6
Td-d Garden variety obsessive Join Date: Oct 2013 Drives: 2009 Sti Hatch; 2015 Audi RSQ3 Location: South Africa Posts: 532 Thanks: 54 Thanked 448 Times in 245 Posts Mentioned: 74 Post(s) Tagged: 2 Thread(s)	Hi Steve - sounds like it's put the car into limp mode - I assume you flashed with ignition in the on position, and no interruptions (door opening, plug in devices, etc.)? I would be surprised if there was a fundamental change in the start-up code.

08-28-2014, 04:34 AM	#13
steve99 Banned Join Date: Dec 2013 Drives: FT86 Location: Australia Posts: 7,996 Thanks: 1,035 Thanked 4,992 Times in 2,983 Posts Mentioned: 598 Post(s) Tagged: 2 Thread(s)	OK I think I found the problem. Looks like a possible error in the definitions for ZA1JD00G ROM for ECUFLASH the checksum module is blank for D00G rom when looking in ECUFLASH ROM info on the A01G ROM its set to "subarudbw" A01G roms flash ok D00G roms either fail on checksum module at end or flash ok and get CANBUSS error car in limp home mode. On non checksum corrected ROM get error at end of flash checksum module fail On checksum corrected ROMS it flashes ok but get CANBUSS error and limp home mode. On an A01G ROM Checksum Module : subarudbw on D00G ROM Checksum Module : (nothing it's blank) @Td-d am I on the right track here ??

08-28-2014, 06:28 AM	#14
Td-d Garden variety obsessive Join Date: Oct 2013 Drives: 2009 Sti Hatch; 2015 Audi RSQ3 Location: South Africa Posts: 532 Thanks: 54 Thanked 448 Times in 245 Posts Mentioned: 74 Post(s) Tagged: 2 Thread(s)	I think that's if - did not come through when I ran the script on the RR definition to convert to Ecuflash. I've edited and uploaded to Github.

User Name		Remember Me?
Password