TSRM/MK3 Supra/Community Fixes
Repair ManualWiring Diagrams
← Back to fixes

No Crank No Start After Long Storage - Multiple Faults (Alarm, Fuel Pump, Vacuum Leaks, CPS Alignment)

EngineadvancedOP Confirmed
Problem

7MGTE would not crank or start after sitting for approximately 15 years. The engine had previously run in this configuration until the crank pulley fell off. After resolving the no-crank condition, the engine still would not start, then once running it idled extremely rough, would die without throttle input, ran lean instead of expected rich, and backfired during cranking attempts.

Engine would not crank at allAfter fixing crank issue, engine would crank but not startNo fuel pressure at the rail despite new fuel pump wiring appearing intactFuel pump jumper wire got extremely hot when shorting B+ and FP, suggesting seized pumpNo audible fuel pump hum from tankOnce briefly running, engine died after 4 seconds at 3000-4000 RPMBackfiring during extended crankingSmoke coming from starter wire area during crankingWould only start with gas pedal fully depressedEngine ran extremely rough and would not idle without throttle inputRPMs bouncing between 1100-1400 when it could idleAir-fuel ratio reading lean (11-14 AFR) when expected to be richIrregular timing light strobe pattern suggesting inconsistent sparkDiagnostic codes 22, 51, and 52
Root Cause

Multiple compounding failures: (1) Loose wire connection in aftermarket alarm system interrupted the ignition/starter circuit causing no-crank condition; (2) Fuel pump seized from sitting 15 years with old fuel in the tank; (3) Extensive vacuum leaks from failed upper intake manifold gasket, bad hose clamp on 3000 pipe to throttle body, leaking cold start injector gasket, leaking ISC valve gasket, completely missing ISC valve diaphragm and spacer, leaking #2 fuel injector O-ring, and torn BOV hose; (4) CPS was jumping a tooth during installation causing incorrect timing signal; (5) Fouled spark plugs; (6) TPS out of adjustment.

Confidence

Moderate confidence — Original poster confirmed this resolved the issue

View Original ThreadPosted August 2025 on SupraForums.com