T43 is now updated and works with early tcms and later os
This is a very intelligent app It doesn't touch the boot area it just checks the OS for compatibility and compatible calibration files
it now has recovery for a calibration failed write, and you can now change the OS safely. again doesn't touch the boot area It has very intelligent sensing
if you've found yourself in a soft brick state from using some other software, This will help you recover to a working TCM but you would have to know what the OS number should be for this to work
it also can change your vin number
I have three of the trans adapts sorted, it's just another two more ill get in the next update.
and the next build I'll get the security linking feature working as well
enjoy
GM-Holden T43 Flasher App Updated Pre-Release 0.4.216
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Re: GM-Holden T43 Flasher App Updated Pre-Release 0.4.216
You do not have the required permissions to view the files attached to this post.
-
Tre-Cool
- Posts: 544
- Joined: Tue Oct 16, 2012 2:17 am
- cars: VY SS UTE, VX Drag Car
- Location: Perth
Re: GM-Holden T43 Flasher App Updated Pre-Release 0.4.216
im not aware of any t43 that uses any security linking.
I spent a couple of days trying to get an early tcm (G1) to take a late (G2) tcm flash on the bench. Here's a summary:
The section we couldn’t flash is the 2nd-stage boot region, 0x20000–0x2FFFF (64 KB) — that’s the “generation” region (G0/G1/G2 differ there), i.e. flash block 0x0B, the start of region-table entry 1 (code 0x33, which spans 0x20000–0x1FFFFF).
Why it’s the one that wouldn’t go:
It’s the only thing standing between G1 and G2 — a generation flash is literally rewriting 0x20000–0x2FFFF.
Erasing it needs $31 02, which arms the erase and the flash algo returns 0xb (7f 31 fd).
Writing it via $34/$36 refuses non-blank flash (7f 36 fe) — no erase-on-write.
And the erase algo itself lives at RAM 0x3F8088, in the Bosch first-stage boot ROM, not in the 2 MB image — so it can’t be decoded or read without BDM.
For contrast, the region below it — the first-stage boot window 0x10000–0x1FFFF — is never erasable at all (that’s what makes RBENTRY recovery always possible), and everything above it (OS 0x30000+, cal, diag, system) flashes fine. It’s specifically that 0x20000–0x2FFFF 2nd-stage boot block that’s locked to software.
RBENTRY is what allows programming with a completly erased tcm btw.
I spent a couple of days trying to get an early tcm (G1) to take a late (G2) tcm flash on the bench. Here's a summary:
The section we couldn’t flash is the 2nd-stage boot region, 0x20000–0x2FFFF (64 KB) — that’s the “generation” region (G0/G1/G2 differ there), i.e. flash block 0x0B, the start of region-table entry 1 (code 0x33, which spans 0x20000–0x1FFFFF).
Why it’s the one that wouldn’t go:
It’s the only thing standing between G1 and G2 — a generation flash is literally rewriting 0x20000–0x2FFFF.
Erasing it needs $31 02, which arms the erase and the flash algo returns 0xb (7f 31 fd).
Writing it via $34/$36 refuses non-blank flash (7f 36 fe) — no erase-on-write.
And the erase algo itself lives at RAM 0x3F8088, in the Bosch first-stage boot ROM, not in the 2 MB image — so it can’t be decoded or read without BDM.
For contrast, the region below it — the first-stage boot window 0x10000–0x1FFFF — is never erasable at all (that’s what makes RBENTRY recovery always possible), and everything above it (OS 0x30000+, cal, diag, system) flashes fine. It’s specifically that 0x20000–0x2FFFF 2nd-stage boot block that’s locked to software.
RBENTRY is what allows programming with a completly erased tcm btw.
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Re: GM-Holden T43 Flasher App Updated Pre-Release 0.4.216
Yea this ain't Holden specific This is GM so some GM controllers do require security linking not just HoldenTre-Cool wrote: Thu Nov 19, 2026 2:02 am im not aware of any t43 that uses any security linking.
I spent a couple of days trying to get an early tcm (G1) to take a late (G2) tcm flash on the bench. Here's a summary:
The section we couldn’t flash is the 2nd-stage boot region, 0x20000–0x2FFFF (64 KB) — that’s the “generation” region (G0/G1/G2 differ there), i.e. flash block 0x0B, the start of region-table entry 1 (code 0x33, which spans 0x20000–0x1FFFFF).
Why it’s the one that wouldn’t go:
It’s the only thing standing between G1 and G2 — a generation flash is literally rewriting 0x20000–0x2FFFF.
Erasing it needs $31 02, which arms the erase and the flash algo returns 0xb (7f 31 fd).
Writing it via $34/$36 refuses non-blank flash (7f 36 fe) — no erase-on-write.
And the erase algo itself lives at RAM 0x3F8088, in the Bosch first-stage boot ROM, not in the 2 MB image — so it can’t be decoded or read without BDM.
For contrast, the region below it — the first-stage boot window 0x10000–0x1FFFF — is never erasable at all (that’s what makes RBENTRY recovery always possible), and everything above it (OS 0x30000+, cal, diag, system) flashes fine. It’s specifically that 0x20000–0x2FFFF 2nd-stage boot block that’s locked to software.
RBENTRY is what allows programming with a completly erased tcm btw.
if you're working on a assumption of G1 and G2 there`s G3 - G4 that's not how I kind of grouped it again it's not Holden specific You've got to look at GM in a Whole.
I had to go through around 650 os coverage of the whole GM-T43 range
out of around that 650 I was managed to group them into 25
I'm not going to touch the boot area and there's a reason for that, Because if I put that in the app and somebody goes to restore the wrong OS She's bricked and you will have to bring out BDM.
So the compromise was we leave the boot area alone, and welcome anybody to try and flash whatever OS they want in to see what will work. And if it doesn't, they can restore it back to their original OS
as you pointed out with the G1 and G2 we were never going to be able to put G1 OS on G2 or G2 on G1 Only way that's going to happen is if we reverse engineer the OS and take parts of the code and transfer it over that way it's the only feasible way.
I designed the app to be safe, So anybody that blows their transmission, and buys a second hand one thats same, doesn't have to go to a mechanic and spend a lot of money. It's a DIY, It's safe and it'll get you back on the road with no issues and no hard bricking.
TCM thats soft bricked, can be recovered as long as no one touches Boot area. and yea there`s two boot blocks for early and older tcms and they changed other parts os too
To date i hold one of the largest XDF catalogues
You do not have the required permissions to view the files attached to this post.
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Re: GM-Holden T43 Flasher App Updated Pre-Release 0.4.216
currently working on a crossover OS which will work with the T43 this'll work for the early 2007 all the way up to 2017
this crossover OS will stop any of the bricking that everybody's been doing and be able to comfortably use it on the T43 APP
this crossover OS will stop any of the bricking that everybody's been doing and be able to comfortably use it on the T43 APP