2014 Porsche bcm damage

**hananmori12** · 8th May, 2024, 02:35 AM

I tried to clean the flux and soldering but still not reading with vvdi and autohex, Thursday I get a used bcm same part number,
I will try to swap the mcu hope it will work

**vov4ik** · 8th May, 2024, 08:13 AM

Let me just confirm, you did remove the components per vvdi diagram as well?
This spot does not look too bad to me, if it is the only damage it should read just fine. Maybe there are issues where components were removed too? Send a good photo of the other areas..
For clock MCU leg should be used and everything else is normal. once done reading you would want to return removed components, settle the crystal back where it belongs and fix the trace...

**hananmori12** · 8th May, 2024, 09:01 AM

Yes I removed the components and its ceramic not crystal, I removed it to clean and I tried to read with and without

I tried to look on everything and I didn’t found any short, maybe the mcu or data is damaged?

The costumer gave me the guy phone number I attached it too

There is a pin out for this mcu?

**vov4ik** · 10th May, 2024, 03:48 PM

Originally Posted by hananmori12

Yes I removed the components and its ceramic not crystal, I removed it to clean and I tried to read with and without

Crystal is the component name (quartz crystal to be exact) and ceramic or metal is the packaging. There is Crystal in Ceramic or Metal package on this board. And yes, yours is ceramic packaged quartz crystal

Originally Posted by hananmori12

I tried to look on everything and I didn’t found any short, maybe the mcu or data is damaged?

It might be if was hooked up with reverse polarity or static-shot. But unlikely. I would check the “via”, the holes that lead trace connection to the back layer of the board. You can use a multimeter with needle probes and check the opposite side of the board. If you send a high-res photo to scale of both sides and enough area visible, I can mark the test points.

Originally Posted by hananmori12

There is a pin out for this mcu?

I’ll dig a pinout later today or tomorrow. Busy week. Do you have a landing pad or stencil for it?

Sent from my iPhone using Tapatalk

**hananmori12** · 11th May, 2024, 02:46 AM

So I got the used bcm with the same part number, the board look exactly the same but chip is 1N35H,

I swap the mcu and its not reading, I put the 1N35H back and its reading no problem, there is any way to read the damage one or I just ~~~~ed up?!

Any other way to get the information from the car and write it to the new bcm?

Tnx

**hananmori12** · 11th May, 2024, 03:27 AM

I tried to read with hexprog too and it was able to read p flash but not d flash, I get error "partition error"

**vov4ik** · 11th May, 2024, 03:33 AM

https://www.nxp.com/docs/en/data-she...XEP100RMV1.pdf

Sent from my iPhone using Tapatalk

**vov4ik** · 11th May, 2024, 03:37 AM

Partition table damaged, read raw by address. Program partition survived tinkering but data partition did not. If you read raw it can be repaired. Another way is create a new partition table w/o formatting (wiping) with just addressing. Not sure what tools are available to you but there are ways to restore it.

Sent from my iPhone using Tapatalk

**hananmori12** · 11th May, 2024, 03:44 AM

Originally Posted by vov4ik

Partition table damaged, read raw by address. Program partition survived tinkering but data partition did not. If you read raw it can be repaired. Another way is create a new partition table w/o formatting (wiping) with just addressing. Not sure what tools are available to you but there are ways to restore it.

Sent from my iPhone using Tapatalk

Thank you for trying to help me!
What tool do I need?

I have vvdi2, prog, autel im508 with xp400, hexprog and autohex,
Ipa clone, xprog clone

**vov4ik** · 11th May, 2024, 03:53 AM

Originally Posted by hananmori12

Thank you for trying to help me!
What tool do I need?

I have vvdi2, prog, autel im508 with xp400, hexprog and autohex,
Ipa clone, xprog clone

Those should be enough. It was a locked chip so you can try reading with vvdi2 (will ask for manual address entry and you should accept what it offers, next partitioning and then writing and reading again. If that fails, you would have to dump front bcm, tcu, and ecm and send it to someone to synchronize to your donor bcm. It gets too complicated for a forum post at that point. https://ecufix-lab.ru/ might help

Sent from my iPhone using Tapatalk

**hananmori12** · 11th May, 2024, 04:07 AM

What about piwis3?

If I can get one and program used/new bcm?

**vov4ik** · 11th May, 2024, 04:47 AM

Originally Posted by hananmori12

What about piwis3?

If I can get one and program used/new bcm?

I have no experience with piwis and used BCM adaptation on Porsche. Can't help. I would expect Porsche to prevent crypto-related part re-use - would be a huge backdoor...
But do not give up on reading that easy, try reading using vvdi with default partitioning and repartition/rewrite

**kazikk** · 11th May, 2024, 02:40 PM

Try this way i repair few Porsche BCM this way.

https://www.digital-kaos.co.uk/forum...=1#post4458224

**hananmori12** · 11th May, 2024, 10:31 PM

Originally Posted by kazikk

Try this way i repair few Porsche BCM this way.

https://www.digital-kaos.co.uk/forum...=1#post4458224

I will try to read with vvdi prog later today.
Also my chip is 5M48H, can I read it though cas4 1N35H ?

And the useb bcm I got its the same part number but mcu 1N35H instead 5M48H so im assuming they are the same type

Edit:
sucks but I read it on cas4 1N35H and try to read on Porsche 5M48H both 32k and 16k and its look bad, look like the data is completely dead right?

**vov4ik** · 13th May, 2024, 03:11 AM

Originally Posted by hananmori12

I will try to read with vvdi prog later today.
Also my chip is 5M48H, can I read it though cas4 1N35H ?

And the useb bcm I got its the same part number but mcu 1N35H instead 5M48H so im assuming they are the same type

Edit:
sucks but I read it on cas4 1N35H and try to read on Porsche 5M48H both 32k and 16k and its look bad, look like the data is completely dead right?

The MCUs are same family but different software level and might (can’t be sure) different memory size and allocation. Check the document I linked for reference.

I will check on the files later on during the week.

Update: All 4 files are just empty. I guess you would have to read the other modules in the car and cook a file for the bcm. Or get a file from a new one, and adapt. Or get a new one and adapt.

Reading through bimmer menu only changes the board diagram, it is still 9s12xep100 with same pinout and different software level according to masket. The real difference is the app that runs on top of it (p-flash) and the user data for it and the specific car (d-flash). The unlocking approach is the same too, described in the manual (page 350 in the document I linked earlier).