OBD Unlock [No bench unlock Required] *** bootmod3 New Feature Release for the S55

[CaryTheLabelGuy]

Originally Posted by Laoschris

Look under the tutorial videos the Cary has put up. I believe he's using a Mac.

[hatepotholez]

Originally Posted by CaryTheLabelGuy

thanks, but how to install the agent on mac? the file extension doesn't open. also there doesn't seem to be another file for macs specifically.

[AlpineWhite_F80]

Originally Posted by hatepotholez

thanks, but how to install the agent on mac? the file extension doesn't open. also there doesn't seem to be another file for macs specifically.

You have to unzip it and you also need to have java. Everything is on bootmod3.net with instructions.
I also struggled a little the first time.

[CaryTheLabelGuy]

Originally Posted by hatepotholez

thanks, but how to install the agent on mac? the file extension doesn't open. also there doesn't seem to be another file for macs specifically.

That is next on my list of videos to make. I’m also going to go over TCU flashing as well as a few others. Just super slammed right now. I’ll get to them probably tonight.

In the mean-time, setup your BM3 account (www.bootmod3.net) and click on the Dashboard tab. Then click on the blue download link. This will download the latest agent. This is a ZIP file that you’ll need move to the desktop and unzip. Once unzipped, download and install JAVA 8 JDK (Not JAVA 9). Once that’s done click on AgentApp.jar (for Mac, start for Windows) once connected to the car’s OBD using the ENET cable. You’ll also need to be connected to the internet for your laptop. This will bring the agent up and will connect to the car and to the BM3 servers. Once you see ********Agent is up******** in the Agent window, refresh www.bootmod3.net. Then click on vehicles and activate your VIN using the KEY provided to you from PTF. Once that’s done, follow the direction in my video.

[AlpineWhite_F80]

Has anyone tried the CS, GTS maps with a new license ?

[M.a.r.k.u.s]

Originally Posted by CaryTheLabelGuy

That is next on my list of videos to make. I’m also going to go over TCU flashing as well as a few others. Just super slammed right now. I’ll get to them probably tonight.

In the mean-time, setup your BM3 account (www.bootmod3.net) and click on the Dashboard tab. Then click on the blue download link. This will download the latest agent. This is a ZIP file that you’ll need move to the desktop and unzip. Once unzipped, download and install JAVA 8 JDK (Not JAVA 9). Once that’s done click on AgentApp.jar (for Mac, start for Windows) once connected to the car’s OBD using the ENET cable. You’ll also need to be connected to the internet for your laptop. This will bring the agent up and will connect to the car and to the BM3 servers. Once you see ********Agent is up******** in the Agent window, refresh www.bootmod3.net. Then click on vehicles and activate your VIN using the KEY provided to you from PTF. Once that’s done, follow the direction in my video.

Any ETA on when the activation issue is supposed to be fixed? I know a lot of people are having the same issue as I am where they can't even activate their VIN. I know PTF is aware of it, just haven't heard if there is any eta on a fix. Since you've been very involved in the whole process, I thought it might be worth asking if you knew.

[shockin330i]

I guess I'll work on my e30 while I wait.

[eandy]

Originally Posted by m4journey

Yes, the stage 2 [93oct] is on my car now and it starts fine. But the warning sign 'Fuel Supply' is on display.

When Agirak was on the same map, his car died when he drove down the road. He got it running again on the stock map but the issue isn't solved yet. I suspect the flash has caused some kind of fuel pump issues. I'm still waiting for my support ticket reply. It's been almost 20 hours and I've been checking my inbox every 20mins for the last 12 hours and can't sleep properly last night!

I need my car running as I normally use it daily but I wouldn't dare to drive it now until it's fixed.

Thanks for updating me. Whatever the outcome it appears that the existing map on the car needs a tweak and therefore you'll need to flash again a different map even if Stage 2 again which has the tweaks to remove these faults.

Is it worth trying a Stage 2 reflash to see if the tweaks have been amended yet? and then if not simply going to stock?

Regarding the tickets I raised one around 30-32 hours ago now and I'm sure most of the similar issues could put minds to rest with a post on here just to outline and acknowledge issues. Such as at present there is 48-72 hours time scale to ticket responses.

We advise don't flash Stage 2 map yet

VIN Unlocks are being investigated and we hope to resolve by Saturday but will update on x,y,z.

Least then people would get an understanding on timescales roughly for the next update in information even if not on a fix because that timescale is unknown.

At present I won't touch my car as only 1 person has posted a successful OBD unlock and flash and that was after an issue and going to a garage.

Everything else is issues, in fact there isn't 1 UK owner that has managed to get this working. Granted it's new tech, everything is snowed under with tickets just to me makes even more sense to put one big post on here that responds and answers most queries and concerns.

[CarbonFoot]

Originally Posted by M.a.r.k.u.s

Any ETA on when the activation issue is supposed to be fixed? I know a lot of people are having the same issue as I am where they can't even activate their VIN. I know PTF is aware of it, just haven't heard if there is any eta on a fix. Since you've been very involved in the whole process, I thought it might be worth asking if you knew.

+1

[tek818]

new activations have been disabled until the bugs are worked out

[proTUNING Freaks]

Hey guys, finally got an update here. Feels like I went to the Moon and back digging for what may have been different here but not seen during beta. We spent all day yesterday and all day today until now and finally have root cause, but need to incorporate the fix for it.

Everything was reviewed in detail to the point that we thought there must be a voodoo doll somewhere someone was stabbing into causing us not to see things and delaying us in seeing this after we just released Still might be possible but that voodoo doll's losing its magic whoever it is

Unlock, re-lock, switching maps, offline flasher, OTS maps, are all fine, except the very last step when coding is done.

None of this was noticed on any of our closed test cars. We had cars from EAS, Eurocharged Canada, overseas customers as well as individuals in the US participate without a single similar incident. Coding is also used by all the people already on the BM3 platform whenever a map is switched but as luck may have it some software versions have additional coding data outside of what we've seen on all the cars done so far that needs to be hooked into our coding step.

Huge thank you to the local Toronto M4 that participated in testing and confirming the root cause of this issue. Now we just need to get it incorporated and resolved. Unfortunately no exact ETA but its not weeks, might take a few days to implement/confirm in testing.

At the moment, the local tester is sorted out by unlocking over OBD, flashing the Stage 2 OTS map (skipping the bm3 coding) and then we simply coded manually with ESys. The other option here would've been and is still an option, to simply do the unlock first and then flash the OTS map as everyone's been doing using the ONLINE flasher which will sort coding out without an issue. We don't like that approach as most people won't understand details of it and we're looking to get this fixed the way it needs to be.

Let us know if any questions and sincere apologies to everyone that may be waiting or has been waiting on updates from us here. There are a handful of us and many of you and we're honestly doing our best to respond to everyone as quickly as we possibly can whether its here or our tech support portal or the facebook bootmod3 enthusiasts page.

[swifty]

Originally Posted by proTUNING Freaks

Hey guys, finally got an update here. Feels like I went to the Moon and back digging for what may have been different here but not seen during beta. We spent all day yesterday and all day today until now and finally have root cause, but need to incorporate the fix for it.

Everything was reviewed in detail to the point that we thought there must be a voodoo doll somewhere someone was stabbing into causing us not to see things and delaying us in seeing this after we just released Still might be possible but that voodoo doll's losing its magic whoever it is

Unlock, re-lock, switching maps, offline flasher, OTS maps, are all fine, except the very last step when coding is done.

None of this was noticed on any of our closed test cars. We had cars from EAS, Eurocharged Canada, overseas customers as well as individuals in the US participate without a single similar incident. Coding is also used by all the people already on the BM3 platform whenever a map is switched but as luck may have it some software versions have additional coding data outside of what we've seen on all the cars done so far that needs to be hooked into our coding step.

Huge thank you to the local Toronto M4 that participated in testing and confirming the root cause of this issue. Now we just need to get it incorporated and resolved. Unfortunately no exact ETA but its not weeks, might take a few days to implement/confirm in testing.

At the moment, the local tester is sorted out by unlocking over OBD, flashing the Stage 2 OTS map (skipping the bm3 coding) and then we simply coded manually with ESys. The other option here would've been and is still an option, to simply do the unlock first and then flash the OTS map as everyone's been doing using the ONLINE flasher which will sort coding out without an issue. We don't like that approach as most people won't understand details of it and we're looking to get this fixed the way it needs to be.

Let us know if any questions and sincere apologies to everyone that may be waiting or has been waiting on updates from us here. There are a handful of us and many of you and we're honestly doing our best to respond to everyone as quickly as we possibly can whether its here or our tech support portal or the facebook bootmod3 enthusiasts page.

So if we are willing to accept deletion of the custom coding in our cars currently, we can go ahead with the flash?

Basically unlock and flash?

[domino_z]

with this new obd development, we really now need a dedicated sub forum for ecu tuning

[chewbakam4]

Really glad you guys found the cause. Sending you good energy from my end! Screw that voodoo doll.

[BIGW0RM]

So is this saying that if you have coding do not purchase BM3 until fixed? Does it work with bimmercode app?

[proTUNING Freaks]

This won't affect the typical coding people do such as rear view mirrors auto-close on lock etc. Those are in separate ECUs in the car. No one codes the DME itself for any features you may have so all that is unaffected.

[tek818]

Are new activations disabled until this update is pushed?

[Agirak]

Originally Posted by proTUNING Freaks

Hey guys, finally got an update here. Feels like I went to the Moon and back digging for what may have been different here but not seen during beta. We spent all day yesterday and all day today until now and finally have root cause, but need to incorporate the fix for it.

Everything was reviewed in detail to the point that we thought there must be a voodoo doll somewhere someone was stabbing into causing us not to see things and delaying us in seeing this after we just released Still might be possible but that voodoo doll's losing its magic whoever it is

Unlock, re-lock, switching maps, offline flasher, OTS maps, are all fine, except the very last step when coding is done.

None of this was noticed on any of our closed test cars. We had cars from EAS, Eurocharged Canada, overseas customers as well as individuals in the US participate without a single similar incident. Coding is also used by all the people already on the BM3 platform whenever a map is switched but as luck may have it some software versions have additional coding data outside of what we've seen on all the cars done so far that needs to be hooked into our coding step.

Huge thank you to the local Toronto M4 that participated in testing and confirming the root cause of this issue. Now we just need to get it incorporated and resolved. Unfortunately no exact ETA but its not weeks, might take a few days to implement/confirm in testing.

At the moment, the local tester is sorted out by unlocking over OBD, flashing the Stage 2 OTS map (skipping the bm3 coding) and then we simply coded manually with ESys. The other option here would've been and is still an option, to simply do the unlock first and then flash the OTS map as everyone's been doing using the ONLINE flasher which will sort coding out without an issue. We don't like that approach as most people won't understand details of it and we're looking to get this fixed the way it needs to be.

Let us know if any questions and sincere apologies to everyone that may be waiting or has been waiting on updates from us here. There are a handful of us and many of you and we're honestly doing our best to respond to everyone as quickly as we possibly can whether its here or our tech support portal or the facebook bootmod3 enthusiasts page.

HUUUGE shout out to Dzeno and the rest of the team. I dont think they slept the past 24 hours.

OTS stage2 pulls like a dream, the burbles are loud and the power delivery is amazing.

World class support and I couldn't be happier with the end results.

[rk604]

Does anyone know if you can use Mac OSX without boot camp right now? Only windows laptop i have is from work, and i doubt IT will give me admin access to do this

[shockin330i]

Originally Posted by Agirak

HUUUGE shout out to Dzeno and the rest of the team. I dont think they slept the past 24 hours.

OTS stage2 pulls like a dream, the burbles are loud and the power delivery is amazing.

World class support and I couldn't be happier with the end results.

Boom

[VLGM]

That's interesting, as for myself I am of the understanding that my DME firmware is too new (12/17 build) and still being uploaded to bootmod's server? I've been trying to activate since yesterday morning at around 0400AEST and still receive the failure.

As for the coding issue affecting some, I've done some minor modifications to a few basic modules but as the guys said nothing really outside of basic comfort options etc that wouldn't impact other areas. I've raised a support ticket and will sit tight, heck I might just even go and try again now. Any idea when we could get a timeline of events to ascertain realistic resolution time?

[BIGW0RM]

I'm scheduled to get this tomorrow. These "issues" whatever they are scaring me. Should I wait to get this???