Member Since: 27 Dec 2013
Location: Staffordshire
Posts: 3
Just wanted to say thanks again to Wiggs. Followed the instructions and all seems well again. Thanks Buddy.
27th Dec 2013 9:14 pm
wiggs
Member Since: 03 Sep 2006
Location: Manchester
Posts: 14372
Glad it's sorted it G4 Gone ...but not forgotten
28th Dec 2013 2:10 am
Eballs28
Member Since: 09 Nov 2013
Location: Sussex
Posts: 20
I have a very similar message but this time it is the HLDF Bootloader MOST waiting download message. Can you help with a fix. This occurred when I got a lost communication message when flashing with Nanocom Evolution (with CTEK MXS25 attached)
28th Dec 2013 5:43 pm
Eballs28
Member Since: 09 Nov 2013
Location: Sussex
Posts: 20
Looks like I need to PM Wiggs for solution
28th Dec 2013 6:30 pm
Eballs28
Member Since: 09 Nov 2013
Location: Sussex
Posts: 20
Also may not be linked but continually get communication error when trying to flash bluetooth module. This was happening before the HDLF error. All other modules including CCF updated fine
28th Dec 2013 6:31 pm
otar
Member Since: 29 Dec 2013
Location: Tbilisi
Posts: 1
I have same issue as above with 05' Range Rover VOGUE.
HLDF CAN BOOTLOADER waiting to start download.
Anyone able to help?
29th Dec 2013 12:24 am
wiggs
Member Since: 03 Sep 2006
Location: Manchester
Posts: 14372
Pm'd you G4 Gone ...but not forgotten
30th Dec 2013 10:12 am
wiggs
Member Since: 03 Sep 2006
Location: Manchester
Posts: 14372
Eballs28 wrote:
I have a very similar message but this time it is the HLDF Bootloader MOST waiting download message. Can you help with a fix. This occurred when I got a lost communication message when flashing with Nanocom Evolution (with CTEK MXS25 attached)
Different issue I'm afraid .
Your not the only one to have this problem after flashing with the nanocomG4 Gone ...but not forgotten
30th Dec 2013 10:20 am
Disco_Mikey
Member Since: 29 May 2007
Location: Dundee, Scotland
Posts: 20786
Member Since: 09 Mar 2009
Location: Littleborough
Posts: 2109
Did you find a solution to it then D_M ?
(Pretty please )Clive
30th Dec 2013 10:42 am
Eballs28
Member Since: 09 Nov 2013
Location: Sussex
Posts: 20
Hi Clive,
Did you get an answer on this?
30th Dec 2013 8:18 pm
crwoody
Member Since: 09 Mar 2009
Location: Littleborough
Posts: 2109
No not yet I'm afraid. I'm hoping that once the new year is in, everyone will be back to normal and some genius will come along with the answer.Clive
30th Dec 2013 8:26 pm
Disco_Mikey
Member Since: 29 May 2007
Location: Dundee, Scotland
Posts: 20786
Was done as part of an SNOTM update. After doing the 2nd update, the screen never booted back up. For whatever reason, there was an issue between the Faultmate and the car. Had to redo the software again, and was fine after thatMy D3 Build Thread
Member Since: 09 Nov 2013
Location: Sussex
Posts: 20
Thanks for that info Disco_Mikey. Obviously we are using a Nanocom, but on that it can't find the ECU for the touch screen so can't flash any software at all to it. Was it the same with the MSV and if so how did you overcome that?
30th Dec 2013 8:49 pm
Eballs28
Member Since: 09 Nov 2013
Location: Sussex
Posts: 20
Wasn't sure whether reflashing the actual Nanocom may make any difference?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum