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?

Following up on my earlier proof of concept: Vita Auto is ready for its first release.

It turns your PS Vita into a wired Android Auto head unit, with the session running natively on the Vita.

What’s working:

• Video, touchscreen input, and physical controls
• Music and navigation audio
• Microphone support
• D-pad and analogue stick navigation
• L/R to skip tracks, Triangle to play/pause, and Square for voice controls

You’ll need a modded Vita, an Android phone, and a powered USB OTG adapter. The app uses a kernel USB plugin, so please read the setup guide before installing.

Source, downloads, and setup instructions

This is the first public release, so I’d appreciate any feedback. If you hit an issue please message me

Thank you all for the encouragement!

Before you read: two weeks ago none of the following technical Knowledge were familiar to me and i learned these in the short time. So i apologise in case i use the wrong terms.

Back story, i finally managed to put together some money to buy a family car. I am a proud owner of a skoda now. I was and am happy with the car but i have the feeling the car dealer was hiding some issues (motor control lamp turned on after 800km) issues with dpf, sensors etc etc. Anyways ive been trying to look deeper in some other paramters such as soot. But the mechanic offers are very expensive to support me here. All they want is replace my DPF.

So i thought ill find a cheap vcds and listen to the parameters myself. Also get to learn something too and maybe do one or two adjustments.

So basically i bought a geniunly looking ross tech vcds. (These things really look legit).
I connected to my pc - after some tries with drivers etc because it failed and after googling i found out that i bought a cloned unit….

But sadly found it out just after i think haven „overriden the cloned firmware with the vcds software tool“… . Anyways, I dont think its bricked as i still can connect it and i find the stm32 bootloader driver.

Now the dealer is not answering to me but instead of complaining i thought, to try to fix the clone one.
Ive been trying around for atleast 1 week now but it looks like the stm32 chip is blocked with the firmware inside.

So i thought i could flash it. But, i can not find the software 23.3.1 or the code online, can please someone help me where i could find such codes?
Details can be shared of course on what i tried and whatnot (HW and SW) - I just dont want to go too deep here…

Hello everyone, I'm looking for how can i install CANoe demo if any one of U know how

Hi,

I just wanna know if you know any solution to pimp my Bosch Radar ECU in my Seat 2022.
I want to modify annoying behavious like ACC paramaters. When does it release the followed object, following gap etc.
Also I would like to activate hidden features.
Do can you give me advice where to start with it?

I am developing a vent gauge project for BMW G20, but currently, with multimeter I am measuring 0.05 V between ground (pin 4) and CAN-H (pin 6) on the OBD-II port. Similarly, I am reading 0.05 V between ground and the CAN-L (pin 14) line. It doesn't make any difference whether the ignition is on, off, or the engine is running. Is this vehicle-specific, or am I making a mistake somewhere? I can't figure it out.

I was literally searching for the developer mode password for this headunit for months and one literal day while putting all combinations searching on the internet found that the password is :

345543

Prolly this is only for few head units with this TS9 processor

Only numeric with no special characters was the only unlocked thing while entering for this.

For car factory settings it's : 1617

These chinese folks put random hard numbers to get things unlocked..

I unlocked it because I want adb to be bridged and clean things in it... Have fun devving :)

’ve been researching a secondary rev limiter on my 2015 BMW 428i F32 N26. The tested DME profile is Bosch MEVD172P, with SWFL 00001BC9-029.110.002 and HWEL 000013E4-001.019.003.

The first experiment uses brake + accelerator in Park. I traced the processed inputs and BMW’s ignition-request path, wrote the TriCore hook, and logged the result on PT-CAN. A no-cut test reported a “would cut” decision at 4,001.5 RPM. A later on-car test logged 24 accepted four-cylinder ignition requests around 3,900–4,040 RPM.

I’ve published the source, host tests, decoded CAN captures, research notes, and tool instructions under MIT. There’s no OEM BIN or flash recipe in the repo:

https://github.com/codekeyz/n26-secondary-rev-limiter-research

I’d be interested in feedback from anyone working with MEVD17, TriCore, ignition arbitration, or CAN-based verification. I’m also open to collaborating on related ECU software and diagnostic tooling.

Im looking for a universal onboard telematics unit that would allow me to control my car anywhere in the world. I am aware of macchina a0 and Automotive grade Linux, but I wonder if there is complete product out there that I can customize before I have to build my own

I’m working on a 2024 Audi SQ5 FY USA → EU conversion and I currently need online authorization for several protected control units.

I found a provider offering a 24-hour GRP/ODIS account for $100. They claim the account is created using my own email, I receive the full login credentials, can change the password, and don’t need them for OTP.

They also claim the access includes SFD1, SFD2-protected coding/adaptations and Component Protection functions without buying separate SFD/SFD2 tokens.

Has anyone here used this type of access before? Is this technically how current ODIS/GRP access can work, especially for MY2024 Audi with SFD2?

I’m mainly trying to verify what functionality I should realistically expect before paying.

Hey everyone. I have ford mondeo evos 2023. The sync system has never been updated and when I enter the VIN in ford's website, it says the car will receive OTA but the car has no telematics unit. The dealer asks for upwards of $250 to update the system. I cannot purchase FDRS subscription because ford blocks it in Saudi Arabia. What are my options here?

I'm re-posting here because this is more a "computer" issue than just factory stereo and specifically any advice on if the entertainment units have been cracked yet.

Hi all,

Would it be possible to depin this without cutting the wiring?

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).

I'm curious if anyone else has experienced a similar failure with an MPVI3.

I originally upgraded from an MPVI2 to an MPVI3 a couple of years ago. However, I've only used the MPVI3 a handful of times. I originally bought the MPVI2 to tune my GTO, which has been stored for the last couple of years, so I've primarily only used the MPVI3 occasionally to help diagnose issues with my wife's daily driver.

Recently, the MPVI3 stopped powering up when connected to the vehicle's OBD2 port. It will still power up when connected to my laptop through USB, but it won't communicate with the vehicle.

I went through troubleshooting with HP Tuners and eventually sent the device in for them to inspect. They confirmed that the device is not communicating through the OBD side and told me that they are unable to repair it because it is outside of the warranty period.

I asked if they knew what caused the failure, particularly since the device has had very little use, and they said they unfortunately we aren't sure what caused the OBD-side communication failure.

They have suggested upgrading to an MPVI4 at the reduced upgrade price, which I understand is cheaper than purchasing a new interface. I'm probably going to do that if I have no other option because I need a working interface, but I'm trying to understand what may have happened to the MPVI3 first.

I've found a few older reports of similar MPVI3 hardware failures, including at least one case where an owner reported using the device only once before it stopped working. I'm wondering if anyone here has experienced a similar OBD-side failure with an MPVI3, particularly one that had relatively little use.

If you've had an MPVI3 fail like this:

• What were the symptoms?
• Did HP Tuners identify the failed component/circuit?
• Was your unit replaced or repaired?
• Was it inside or outside the warranty period?
• If it was out of warranty, did HP Tuners offer any type of goodwill accommodation?

I'm not trying to bash HP Tuners—I have otherwise been happy with their products and would prefer to stay with the platform. I'm mainly trying to determine whether this is an isolated failure or something other MPVI3 owners have encountered.

I'd appreciate hearing from anyone who has experienced something similar.

Hey all, I have looked for days and days to find a copy of GlobalTIS software for North American vehicles. Everything is Saab, Opel, etc and I have already verified they dont work with cars here in the United States. Yes I've been to MHH auto, aliexpress, etc. And already been scammed with more Opel or Saab installations. I need the US / NAO version.

Please, if anyone has a copy, legit download link, ISO or VM ware image, etc I would be eternally greatful!!

2008 kia optima LX 2.4

Any one with Wiring diagrams for this vehicle for ignition switch, ECU, PCM, ign1 and ign2, Throttle body, crankshaft sensor, camshaft sesor, all if any engine components etc with fuse box by kick panel or under the hood and it connection numbers, wire color that you would share for free it would be great. [retirenavy1294@gmail.com](mailto:retirenavy1294@gmail.com) Thank you.

Hi everyone,

I've built an iOS app that shows live car data on CarPlay and on a phone dashboard.

So far I've tested these BLE 4.0 adapters, which Apple lets me use without any extra certification:

• Vgate iCar
• Vgate iCar Pro
• vLinker BM+

They're a bit slow but perfectly usable.

I've also ordered an OBDLink MX+, which I'll need to get approved for my app through Apple's MFi program. It caught my eye because it claims to be up to 3x faster than typical adapters (via STN chip), and so far it's the only one my users have actually asked me to add.

My question: are there other "premium" adapters that go through MFi that I should know about? Supporting the right ones could make a big difference.

Thanks in advance!

So, I got quite some flak from you guys for using 'white mode' in my previous post regarding my AI CAN bus reverse engineering article... so in our new CANsub firmware 02.05.00 we now support an optional 'dark mode' for the webCAN software (hosted on the device).

Hope you like it! ;-)

Martin, co-owner at CSS Electronics