Hello
I am trying to fix a handful of bricked e67s that had the wrong os written on them or other odd reasons they bricked.
Year range was 09-14 and I also have a gm performance ecu that bricked too.
using the can method some of them do read the info but they will not read out , it gets a error or gets stuck.
most of them have corrupt serial numbers
how do i recover these ecus ? also where do i find clean stock files to use for writing?
thank you
Recovering Bricked e67 ecu
-
- Junior Member
- Posts: 9113
- Joined: Mon Jul 18, 2005 9:33 pm
Re: Recovering Bricked e67 ecu
The one that can read info should be able fixed by can bus. Others need bdm method to fix.
-
- Junior Member
- Posts: 31
- Joined: Sun Jul 26, 2020 5:13 pm
Re: Recovering Bricked e67 ecu
If they are responding at all, even incorrectly they can likely be saved with canbus like the e38's but it's not a short process..
Guessing the seed and key are messed up, sometimes your lucky and they give a seed of 0000 and are already unlocked. Other times key is the same as seed, and usually it's just messed up.. Different OS's will look/use the eeprom segment differently and when you flash in incompatible OS the seed-key is not where it used to be so it's reading other data..
You can brute force the key which can take up to 7 days, this is with a 2 byte seed-key. I have no idea on a 5 byte seed key but It's simply not possible.
Once you get it unlocked you can push the read/write kernel and bring it back to life..
You can add "readcan Seed 1A 27 r b" to the script to see if it's responding and see what the seed is..
btw.. This is all going off with my belief that the E67 is very similar to the E38 ecm's and how they can get soft bricked the same way with a mismatched OS.
Guessing the seed and key are messed up, sometimes your lucky and they give a seed of 0000 and are already unlocked. Other times key is the same as seed, and usually it's just messed up.. Different OS's will look/use the eeprom segment differently and when you flash in incompatible OS the seed-key is not where it used to be so it's reading other data..
You can brute force the key which can take up to 7 days, this is with a 2 byte seed-key. I have no idea on a 5 byte seed key but It's simply not possible.
Once you get it unlocked you can push the read/write kernel and bring it back to life..
You can add "readcan Seed 1A 27 r b" to the script to see if it's responding and see what the seed is..
btw.. This is all going off with my belief that the E67 is very similar to the E38 ecm's and how they can get soft bricked the same way with a mismatched OS.
Who is online
Users browsing this forum: No registered users and 3 guests