I have a clio 4, the car will not turn off unless the start button is pressed multiple times. No fault codes with Clip in any of the computers, keycard is seen in slot, starter button works on the live data PIDS.
As you know, finding and downloading the necessary firmware for Mercedes units is not so easy. Basically, they can be downloaded from Xentry Update Service (XUS), but as you know, it is very difficult to make it work. Initially, I wanted to make a program that would be an alternative to XUS.
But, over time, I decided to add more functionality: searching for software by Hardware number. Some will immediately say, what's new here, there is already SW Finder and they will be right, yes, it has even more functions than this one.
But, try searching for firmware, say, for ME97, IC222, for such units where more than one firmware is needed. Yes, in SW Finder you can find such data (where there are numbers of the entire software assembly, and not one by one), maybe even 3 and that's it. There are 108,781 data lines in the SW Finder database, we currently have 100,363 (on the day of writing this article) and this data is constantly updated.
I did not use data from 108,781 lines from SW Finder, so it was easy to type a beautiful number, but there is a lot of unnecessary data, which almost always interferes with the normal selection of software. In our case, the data in the program was taken from Xentry itself, or rather from akttab files (but very little, there is also a lot of unnecessary information there), all the other data (a very large part) was taken from working cars!
You can also find encodings in the program. Remember, a car arrived to you, someone did something there and you need to return the encodings to the stock state. Of course, many who do such work already have saved encodings from many cars, but remember how difficult it is to find the right one there!
With the help of this program, this can be done in a few seconds, well, maybe minutes. And imagine that when selecting, you can even look at the configuration of the car from which these encodings were taken. What if you search for encodings by the configuration number?)
The program has several search options:
- Search by software number. Everything is simple here, we search for the required firmware by the software number, download it or copy the link (convenient for remote work).
- Search by hardware number. In the search window, we write the HW number and the program automatically starts the search and shows the numbers of all firmware that are in our database with this HW number, or a collection of numbers (if the unit has several firmware). It will also show possibly compatible hardware numbers, but this is not a fact that they are compatible, you need to be careful here! Such software will be highlighted in red.
- Search by unit name. In the search window, we write the name of the unit, for example MED40, VGS4NAG2, IC_204 and click on the "Search by ECU" button.
- Search for encodings. Here the search is much more advanced. You can search by VIN number, maybe you'll get lucky and our database contains encodings from this particular car. You can search by car model, chassis number, unit name, Hardware number and also by Software number.
- Search by configuration number and body. For example, you can search for code 642 for chassis 213, find the VIN of a car that has the required configuration and it is in the database, then double-click on the VIN, all the codings from this car open at once.
- There is a large database of cbf and smr-f files from different versions of Xentry and DAS, including engineering ones.
The database contains data mainly for relatively new cars, approximately from 2005 to the latest ones, you can even find an update for units on 206, 223 and so on!
Not always, but often in the database you can see the VIN number of the car from which the data was taken, this will be very useful when selecting software for motor cars, automatic transmissions and even for head units. Now, when searching, a filter by VIN number has been implemented, or rather by model, for example 204054.
For HU204, HU45/HU47, in addition to software numbers, you can immediately see the telematic disk number, which is needed to flash these software..
Attention!!! The program may have an incorrect block name and version! I repeat, the data is mainly taken from working cars, therefore, I estimate their HW-SW compatibility accuracy at 97%, but still, different blocks have their own nuances, all this needs to be known, taken into account, nevertheless, everything you do, you do at your own peril and risk, you need to understand this!
The program is sold with a one-year subscription, linked to HWID (for one system)!
A one-year subscription costs - $ 220 A one-month subscription costs - $ 60
You can find autompatic payment method in text file here.
i am selling flex hardware in a box like new. The price of the new one is 1250e. My price is 800e. It is necessary to pay 150e for the change of ownership.
There's been a lot of topics about adaptation fail issue, but my situation is kind of strange. How it all happened step by step:
1. Gearbox was 100% technically fine, was serviced at official dealer ~50 kkm ago, no problems ANYTIME. Mileage 150 kkm. Car had problem with rear diff and after changing fluid and running adaptation, decided to do gearbox adaptation as well. Got stuck at P287C00 (abbruch weil gangsteller EvenLow negativ eingelegt Position außerhalb toleranz)
2. Vediamo update and coding - error still there
3. Dump read with flex and applied popular dump fix - error gone, but couldn't drive normally, car managed to get into D1 and R only after warming up (drove fine in these gears), cannot get to D2. Trying to run adaptation - same error. For me it looks like gearbox will work if had any adaptation data in EEPROM, but it was deleted when trying to do adaptation
4. Contacted person tried another way of patching dump, but this time after flashing 287C00 was still there. I didn't rewrite the flash before trying this last fix though.
From what i see only possible solution would be used board and custom made EEPROM, since I believe even new board from the dealer wouldn't help in this situation. Maybe someone could help? As I am new I don't expect to get anything for free, just need to sort this issue somehow
I attached EEPROM files I have. Unit is A0054463710 (FBS4), fw 0009026651 Car W176 16'
So ive recently deleted my dpf, and bought a kess. ive gone to take the file off my car and then it told me you can not read off this car, only write. I dont want to change the map as i actually really like the stage one that i have. But i suppose there is nothing i can do about that.
So does anyone have a stage one file for the MK7 GTD with the CUNA engine? Prefereably with the dpf deleted and NOx, or even a stage 2 if thats around? Sick of having an engine light on my dash.
as the title suggests i am seeking help to remove immo for this 4D56 denso ecu, I can supply eeprom read too if required but research tells me that flash should be enough
hi i need help with crash clear on this bmw g12 https://easyupload.io/15vr8y here is link with dump if anybody can help me
65.77-9890597-01 acsm5 A3C00183502
eeprom 95512
Asking for advice.
I bricked an MJ9DF HW001 while trying to disable AdBlue (didn't want to wait 2 hours for the stock firmware readout and downloaded a stock file from the internet and flashed it). After turning on the ignition, something started crackling in the area of the block with relays. I was trying to disable AdBlue because there was only a 150 km reserve left.
Then, I opened up the ECU and started flashing all possible firmware for a similar car with the same engine and ECU via JTAG. After turning on the ignition, the crackling stopped. The starter turns, but the engine doesn't start. It fires up with brake cleaner but only runs on it.
I bought a new ECU identical to the original one for auto-linking (virgin). Still no start. Start is permitted. Synchronization is present. The dashboard shows an AdBlue error. The Launch scanner doesn't detect the SCR module, so there's no way to reset it. Could the AdBlue counter have reached its limit and blocked the start?
I'm completely lost at this point. Essentially, the ECU just drops the rail pressure, whether it's the original or the new one. No errors related to AdBlue are displayed in the ECU, whether with the stock firmware or one with AdBlue removed. The situation is the same in both cases.
VMProtect can fall in love with a VM.