r/CarHacking

Hi awesome community
So I bought a Gen 2 2011, 161,000km (100,000 miles), modifications were already put on the car by the previous owner;
- Cobb catback exhaust
- Cobb SF Intake + Turbo Inlet
- GFB BOV
- EGR block off and delete (CEL on dash as result)
- Cobb Downpipe (Wasn’t listed but it looks like it is)

Obviously I have great concerns for the fuel pump and I have an Autotech HPFP on the way and intend to install asap.

The car came with an unmarried cobb accessport, i’ve been using it to check engine codes and I’ve currently got:
P0403, due to egr delete
P0421, I believe due to downpipe
and… P0171, for obvious reasons

I currently have Stage 0 (Stock) ECU map on the access port and am just keeping an eye on the gauges to ensure I’m not straining the engine until the hpfp arrives.

Although the cobb accessport has a stage 1 economy + Sf map, which I was wondering would be a safer alternative to use temporarily until I install the hpfp and get a custom tune.

Is it safer to just keep the current stock ECU map or is it worth switching to the economy + sf map so that my engine stops reading lean conditions?

I am looking for owners of recent Volvo and Polestar models, seeking help to better characterize a security vulnerability that I found while digging into the software stack of my own car, a Volvo EX30. Before I make the responsible disclosure to Volvo Cars, I'd like to confirm whether it affects other models as well.

This is where I need some help: I need access to the software running on the AAOS (Android Automotive OS) infotainment systems of potentially affected models. Of course only the system part of the head unit, nothing that is individual to a vehicle (device/vehicle ID, user generated data, etc.).

The particular brands/models I'm interested in:

• all Volvo Cars models that use AAOS ins their infotainment system (vehicles made in the last 3-5 years or even older models that might have gotten it as an upgrade)
• all Polestar models that use AAOS in their infotainment system (vehicles made in the last 5-6 years)

I suspect that the issue predates the arrival of AAOS, but I'm not really familiar with the Sensus architecture. Still, if somebody has a file system dump from an older Sensus infotainment system, I'd like to take a look at it too.

Here's what I need:

• a dump of parts of the file system like /product, /system, /system_ext, /vendor, etc. (or an OTA update package, i.e. *.VBF files)
• name of the vehicle model
• model year
• software version

I also wrote a non-instrusive app that can extract a file system dump from an AAOS device (of course not everything, just what any 3rd party app can read), it's available on GitHub. You can compile it yourself or I can give access to my Google Play Internal Testing track.

I'll not give away any details about the vulnerability itself before I gave Volvo a chance to fix it, so don't even ask.

If somebody is willing to help with this, I wrote a more lengthy page about the system dumper app, my motivation, myself (I don't try to hide my identity) and how you can contact me.

Of course I understand that anybody could write this with malicious intent in mind. I don't think there's much more I could do to convince people that my intentions are honest. If I don't get useful feedback/help, I'll just hand in (to Volvo Cars) what I know about the EX30 and hope they'll actually fix it. The worst that could happen is that they do an ineffective fix for the EX30, they don't fix any other models (claiming that they are not affected by the issue and I cannot prove them wrong) and in reality they all remain vulnerable and somebody with malicious intent starts working on this. In that scenario there's still the option to involve regional authorities (US, EU, etc.) and the media. Both can exercise the necessary pressure to make an actual fix happen (there has been precedent with models from other automakers).

My original MED17.1 ECU is dead and unreadable. I have a matching Bosch MED17.1 donor ECU. I need to read the IMMO 5 data from my car's BCM2/key and adapt the donor ECU so the factory immobilizer stays intact."

Remote Support ODIS Online Immobilizer Service

Unfortunately, through my own mistakes, I lost my 2023 toyota Camry key fob in the airport.

I do have a spare key so it isn't the end of the world, but I would like to be able to program a new one. If I bought a blank remote, are there any open source tools tutorials that could help me program the new key properly?

I need help seeing if the live view CAN sniffing is compatible with peoples setup. Would love any comments or criticisms. I think the Reverse Engineering is actually quite novel on this website!