You figured it out already but maybe that would help other people:
No need to turn on ECU twice also no need to count to 6 Just ground boot pin, turn power ON and you can disconnect boot pin immediately. Then generic BOSCH 0,5/1MB (depends on sw version), then ID (to make sure connection established) and then just Read.

Qhhj xdf and ols files are defined fully in this thread
Look around

Hi all,

I'm a veteran with Audi ME7 from 15 years back, but I got myself a fun old project car, P80 V70 MY00 with B5234T3 (240hp, ME7). I've been flashing the ECU on the bench (bootmode or MPPS over CAN from connector), but it's annoying to have to pull the ECU every time for that..
I've read through this whole thread and given the different tools shared here a try with a Super J2534 cable (Mongoose JLR clone, with atmel chip) on Windows 11, here's bit of a summary in case someone else wants to try OBD flashing a P80 ME7 Volvo, or has some input on what to try and what works:
- @Prometey1982 's Volvologger downloaded from a cloud storage works, I can log my ECU successfully (10ERHJ)
- Prometey1982 Volvoflasher shared from cloud storage ("P1 ME9 flashing succesful version") fails with Bad any_cast when specifying baud rate 250000, with 500000 it attempts but of course doesn't connect
- Newest commit from Github (https://github.com/prometey1982/VolvoTools) compiles but doesn't find any flasher adapters - any idea what's wrong, should I try some older commit ID?
- Openmoose_og downloaded from http://www.openmoose.net/blog/?page=Downloads doesn't start at all
- Openmoose Redux (beta 10) finds the J2534 adapters from registry, but only says "DiCE is not connected" although correct adapter is selected and connected
- Openmoose Renatus (beta 7) starts when I put the system date a few years back (otherwise it complains the build is too old), it connects to the Mongoose adapter, connects to the car and gets the ECU ID. Flashing attempt does a lot of CAN bus resetting and relay clicking with the dash flashing but does not proceed from "Connecting to ECU" stage. After giving up the engine starts, but dash was dead. Disconnecting the battery brough the dash back to life.
- The VIN license tied Willett Run Automotive flasher , "FlashSuite_BIN.exe" doesn't seem to work with the Mongoose JLR, it also just complains that DiCE is not connected.
- MPPS (legit licensed version, the last V22.4.3.6) also fails to put the ECU in programming mode in the car, but flashes succesfully on the bench from the connector

So currently I'm thinking there might be two ways forward, finding a way to get Prometey1982's Volvoflasher to work as it's supposedly capable of flashing P80 cars, it would just need to be a version that both properly sets baud rate and finds the adapters, or maybe buying a chinese DiCE clone just for flashing to use the FlashSuite_BIN. It's strange that it does list the adapters but just won't connect.

Question about the fuel pump s60r2004. I want to replace the pump, the fill level at idle is 45%. I recently removed the basket from the pump and cleaned it, which improved performance, as before cleaning I had a maximum of 420-440 kPA. Additionally, a problem has arisen because the pump does not maintain fuel pressure overnight; even after turning off the engine, the pressure drops immediately. There are no leaks, the pump is tight, and fuel does not flow back through it. The fuel pressure regulating valve is probably damaged, I don't think it can be replaced. Here are the original basket numbers 8616703 and Bosch number 0580314032, this is the feed pump number 0580454022, and this is the overflow pump number 0580454023. What is the best thing to install to work well with the pump module? Is there a patent for this valve that leaks when the engine is turned off? Maybe a pump with a higher capacity, the original one probably has 170 l/h.

Nice What head gasket did you use? 2.3 paper one or R steel one?

You'r probably triggering Torque Monitoring error.
You can do 2 things. "Hack" MAF scaling to cheat ECU so it see lower load. Messy, hard to do and will cause even more problems.
Rescale TQ-MON maps. That is a bit tricky. You need to decompile software for this to be 100% sure what and where to modify.
Basically tq-mon maps start at 0x17800h. In your sw. it ends at 0x17A52.
Somewhere in the end of the area there are a few bytes that are the checksum of the whole area. You need to rescale TQ-MON maps (mostly KFMZPxx_UM maps) to match your KFMIRL/OP

Also your approach to the load tune is wrong i guess. Load is not linear function of the boost in the rpm range. When you set LDRXN to flat 195% you will get messy boost curve.
If you can't scale LDRXN properly you can alternatively use DHBN to set boost curve.