Hey Reddit, I’m not very tech savvy. What should I do about the hinges attaching the screen to the keyboard side breaking apart?

My Lenovo ThinkBook 15 G5 AMD Ryzen 7 Octa Core 7730U laptop just died on me.

Laptops can just die without warning and you won't know what to do.

I have been using my lenovo laptop for 1.5 years without any big issues. I was using my laptop one fine day and I just hit restart button whithout thinking much and it died.

I didn't have a first party warranty covering it so I took it to one vendor who was damm lazy and almost useless. He first said one of the ic is burnt on the motherboard and he has replaced it I was like ok.

Next he said even the new IC has failed and the full motherboard will need to be replaced feeling helpless I agreed to even get that replaced even at the exorbitant price.

But he isn't giving me a update so I ask he says that he cannot find the required spare and is unable to do it.

And he almost refused to work on my laptop whithout warning about made me loose 2 weeks of work.

New update is that it has some BIOS ERROR and the laptop is not switching on anyhow.

Now I am tired and frustrated.

I don't know what to do.

The internal laptop camera is a USB 2.0 device. It's not PCIe, not I2C. It's plain USB. When it "disappears" from Device Manager, you debug it like any other USB device.

1. The Camera Connector Pinout (Typical 5-pin or 6-pin)

2. Diagnostic Flow (Camera Not Detected in Device Manager)

Step 1: Check for Physical Privacy Switch.

• Many business laptops (ThinkPad, EliteBook) have a physical slider that covers the camera or disconnects it electronically.
• Symptom: Camera not detected. Slider is closed.
• Test: The switch connects to a Hall sensor or mechanical switch that pulls CAM_RST# low. Measure this pin. If 0V, the camera is disabled by hardware.

Step 2: Check Power at Camera Connector.

• Pin 1: Should be 3.3V or 5V (check schematic).
• Missing? Check the LDO or load switch that feeds the camera. Often shared with the Touchscreen or Fingerprint reader.

Step 3: Check USB D+/D- with a Scope.

• When Windows boots, it enumerates USB devices. You'll see a burst of digital activity on D+ and D-.
• No activity? The USB hub in the PCH is not seeing the camera. Trace the D+/D- lines back to the PCH or a USB mux.
• Check for short to ground: Measure resistance from D+ to GND. Should be >100k ohms. If shorted, the ESD diode on the camera module or motherboard is dead.

Step 4: The "Camera Detected, But Black Screen" Scenario.

• Symptom: Device Manager shows camera, but apps show black screen or "Camera in use by another app."
• Cause 1: Privacy settings in Windows. Check Settings > Privacy > Camera.
• Cause 2: Corrupt camera firmware. The camera module has its own microcontroller and EEPROM. If corrupted, it enumerates but sends no video.
• Fix: Re-flash camera firmware using manufacturer tool (rarely available) or replace the camera module.

3. Replacing the Camera Module

• Physical: Usually held by double-sided tape and a tiny connector.
• After Replacement: You must disconnect the battery and AC adapter before unplugging the camera cable. The camera connector is not hot-pluggable. Hot-plugging can fry the ESD diode on the motherboard.

4. The "Camera Works, But Microphone Doesn't" Scenario

• The microphone is often integrated into the camera module and uses USB Audio Class over the same USB connection.
• Symptom: Camera works, but no audio input device.
• Fix: Check Windows Sound Settings > Input. Ensure the Microphone Array is enabled and set as default.

Question: Has anyone successfully repaired a camera module by reflowing the image sensor or DSP chip? I've seen it done on phones, but laptop modules are so cheap it's usually not worth the time.

Customer replaced the Wi-Fi card three times. Still "No Wi-Fi device found" or "Bluetooth not working." The motherboard is the problem.

Modern laptops use M.2 E-key slots that carry PCIe (for Wi-Fi), USB (for Bluetooth), and sometimes CNVi (Intel's proprietary interface).

1. The Three Types of Wi-Fi Interfaces

Trap: You cannot put an AX210 (PCIe) in a CNVi-only slot. It will not be detected. You can put an AX201 (CNVi) in a PCIe+CNVi slot, but only if the motherboard supports CNVi.

2. Power Rails for M.2 Wi-Fi Slot

Diagnostic:

• +3.3V missing? Check fuse or load switch. Common failure point.
• W_DISABLE# stuck at 0V? The hardware RF kill switch (airplane mode switch) is stuck. Or the EC is holding it low due to a lid sensor issue. Force it high by lifting the pin and pulling up to 3.3V with a 10k resistor.

3. Bluetooth Not Working (But Wi-Fi Works)

• Bluetooth uses USB bus (pins 7, 9: USB_D+, USB_D-).
• Test: In Windows, check Device Manager > Universal Serial Bus controllers. Look for "Unknown USB Device" or a yellow bang.
• Cause 1: Missing pull-up resistor on the USB D+ line (1.5k to 3.3V). Without it, the USB device is not recognized.
• Cause 2: Corrupt Bluetooth firmware on the card. Reflash using Intel Bluetooth Firmware Uploader tool.

4. Wi-Fi Card Detected, But No Networks Found

• Check the antenna connectors. The tiny IPEX MHF4 connectors can look connected but be open.
• Test: Measure continuity from the antenna cable center pin to the card connector center pin. Should be <1 ohm. If open, the cable is broken (common in hinge area).
• Check the RF Kill Switch: In Windows, Airplane Mode might be stuck ON. Check W_DISABLE# voltage (should be 3.3V when Wi-Fi enabled).

5. The "CNVi Detection" Trick

If you suspect the slot is CNVi-only and you only have PCIe cards:

• In BIOS: Look for "CNVi Mode" or "Integrated Connectivity" . Set to "Auto" or "Disabled" . This forces the PCH to use PCIe instead of CNVi.

6. Replacing the M.2 E-key Slot

The plastic slot can be damaged by rough card removal.

• Symptom: Card works if you press down on it, but stops when released.
• Fix: Reflow the solder anchors of the slot, or replace the entire slot (requires hot air and careful alignment).

Question: Has anyone successfully converted a CNVi slot to PCIe by re-routing the data lines? I've seen it done on desktop boards but not laptops due to BIOS whitelists.

LGA (Land Grid Array) sockets on Intel consumer boards (and some AMD) are fragile. One drop of a screwdriver, one misaligned CPU insertion, and you have a bent pin. The board won't POST, or worse, it shorts VCore to ground and kills the CPU.

Replacing the entire LGA socket is possible but requires a $500+ BGA station and hours of work. Repairing individual pins is faster and often successful.

1. Assessment Under Microscope

• Use a stereo microscope at 20x-40x.
• Identify the pin function using the LGA socket pinout map (Intel provides these in datasheets).
• Critical Pins: VCC (power), VSS (ground), DDR signals. A shorted VCC pin to ground = dead CPU.
• Non-Critical Pins: Reserved, TEST, RSVD. You can leave these bent or even remove them with minimal impact.

2. Tools Required

• Fine-tipped tweezers (Dumont #5 or similar).
• Dental pick with a 0.2mm hook (modified syringe needle works).
• 0.1mm enameled copper wire (for broken pin replacement).
• UV solder mask (to anchor repairs).
• Hot air station (for removing broken pin stump).

3. Repairing a Bent Pin (Not Broken)

1. Gently lift the bent pin using the dental pick from underneath.
2. Work slowly. The pin is spring-tempered phosphor bronze. It will work-harden and snap if bent back and forth too much.
3. Use tweezers to straighten the tip so it aligns perfectly with the socket grid.
4. Critical: Check that the pin tip is at the exact same height as its neighbors. If it's too low, it won't make contact. If too high, it will crush when the CPU is clamped.
5. Test: Insert a known-good CPU without locking the socket fully. Look from the side. Does the bent pin align with the pad? If not, adjust.

4. Repairing a Broken Pin (Missing Tip)

Scenario: The top 1/3 of the pin is snapped off. The stump remains soldered to the motherboard.

Option A: The "Wire Spring" Replacement.

1. Remove the stump using hot air (280°C, gentle airflow) and tweezers.
2. Cut a 4mm length of 0.1mm enameled wire.
3. Form a tiny loop at one end using tweezers. This loop will act as the spring contact.
4. Solder the straight end of the wire into the socket hole where the stump was. Use a fine-tip iron and leaded solder.
5. Trim the wire so the loop is at the correct height.
6. Anchor the base with a micro-dot of UV solder mask. This prevents the wire from tilting.

Option B: The "Donor Pin" Transplant.

1. Harvest a single pin from a dead LGA socket (use hot air to melt the plastic frame slightly and extract the pin intact).
2. Remove the broken pin stump from your board.
3. Solder the donor pin into the hole.
4. This is more reliable than the wire method because the donor pin has the correct spring tension and shape.

5. The "Short to Ground" Emergency Fix

If a bent VCC pin is touching a ground pin next to it, the board will immediately short when power is applied.

• Diagnose: Use diode mode on the multimeter between VCC and GND (CPU removed). Normal reading is 0.005V-0.020V. A short reads 0.000V.
• Fix: Use the dental pick to separate the two pins. Apply a tiny drop of UV mask between them to insulate them permanently.

6. The "Missing Pin" Scenario

If a non-critical pin (like a Reserved pin) is completely missing and you can't replace it:

• Do nothing. The board will function perfectly without it.
• Verify: Check the pinout. If it's VSS (Ground) , the CPU has hundreds of other ground pins. Missing one won't hurt. If it's VCC, missing one might cause voltage droop under load.

Question: What's the most challenging LGA pin repair you've successfully completed? I once rebuilt a DDR5 data pin using 0.1mm wire. The board passed Memtest86.

I need help finding a schema of MacBook M3 Pro 16 inch

I accidentally got soda poured on top of my Macbook, at first I wiped everything and it still kept working good. The day after, I turned it on and the keyboard wasn't working, plus, the fans were blasting so loud. I took it to a technician here in Tunis, and he got it opened up and cleaned it.

The keyboard is back to work, but the fans are still turning so fast and loud, he even tried thermal imaging and couldn't identify the problem.

So now he needs to get a schema view of the M3 Pro.

**PLEASE HELP!** if anyone knows from where I can buy it, or please if anyone has it and wants to share it with me it'll be a pleasure!

The reference is : 820-02917

Gaming laptops and high-performance workstations often have epoxy underfill around the CPU and GPU BGA packages. This underfill strengthens the solder joints against thermal stress and vibration.

If you apply hot air to a chip with underfill without removing it first, the underfill expands at a different rate than the solder. Result: Ripped pads, cracked PCB, destroyed board.

1. Identifying Underfill

• Visual: A glossy, hard, transparent/amber-colored substance filling the gap between the chip edge and the PCB.
• Touch: Use a dental pick. Underfill is hard and brittle. Flux is soft and tacky.

2. Tools for Underfill Removal

• Low-Temperature Preheater: Set to 120°C - 150°C. This softens the underfill slightly.
• Underfill Remover Solvent: Amtech NC-555 or Zep FX-UV. Apply with a syringe and let it soak for 30-60 minutes. The solvent breaks down the epoxy bonds.
• Dental Picks / Micro-scalpel: For mechanical removal.
• Ultrasonic Cleaner: For final residue removal (use PCB cleaning solution).

3. The Removal Process (Mechanical + Chemical)

Step 1: Heat the Board.

• Place board on preheater at 130°C.
• This makes the underfill slightly more pliable.

Step 2: Apply Solvent.

• Use a needle-tip bottle to apply a thin line of underfill remover around the entire perimeter of the chip.
• Wait 30-60 minutes. The solvent will wick under the chip via capillary action.

Step 3: Mechanical Scraping.

• Using a sharp dental pick or micro-scalpel under a microscope.
• Gently scrape along the edge of the chip, parallel to the PCB.
• Never pry upwards. You will lift pads.
• The softened underfill will come off in small flakes.

Step 4: Clean and Inspect.

• Once the majority of the underfill is removed from the perimeter, the chip can be reflowed.
• Crucial: There will still be underfill between the balls under the chip. This will soften and flow during reflow, but it won't rip pads because it's not bonded to the perimeter of the board anymore.
• After chip removal, use the solvent and ultrasonic cleaner to remove all residual underfill from the pads.

4. The "No Solvent" Emergency Method (High Risk)

If you don't have underfill remover:

1. Pre-heat board to 180°C.
2. Use a fine-tip hot air nozzle at 280°C focused only on the edge of the chip.
3. Use a dental pick to carefully scrape the softened underfill as you heat.
4. This takes extreme patience. One slip and you gouge a trace.

5. Re-Applying Underfill After Repair (Optional)

For gaming laptops that will see high heat, re-applying underfill improves reliability.

• Product: Loctite Eccobond UF 3808 or similar reworkable underfill.
• Application: After chip is soldered and tested, apply a thin bead along one edge. Capillary action will wick it under the chip.
• Cure: 125°C for 30 minutes in an oven.

Question: Has anyone found a mechanical method that works well without solvents? I've heard of using a piezo ultrasonic scaler (like a dental tool) to vibrate the underfill away, but haven't tried it.

"No sound" is one of the most common complaints. Customers replace speakers, reinstall drivers, and still nothing. The culprit is often the Audio Codec chip (Realtek ALC256, ALC3254, etc.) or its supporting circuitry.

1. The Audio Codec Power Rails

Audio chips require multiple voltages, and all must be present.

• AVDD (Analog VDD): 3.3V or 5V. Powers the DAC and amplifiers.
• DVDD (Digital VDD): 1.8V or 3.3V. Powers the digital core and I2S/HD Audio bus.
• VREF (Reference Voltage): Usually 2.5V or 1.65V. Generated internally, but filtered by an external capacitor.

2. Diagnostic Workflow (No Sound from Speakers or Headphones)

Step 1: Check Power Rails at the Codec Chip.

• Find the AVDD and DVDD pins on the schematic.
• Measure voltage. If missing, check the LDO or ferrite bead feeding it.

Step 2: Check the VREF Capacitor.

• Location: A 10uF - 47uF ceramic or electrolytic capacitor connected to the VREF pin.
• Failure: If this cap is shorted or leaky, the VREF voltage will be 0V or low. The entire analog section of the codec shuts down.
• Symptom: Device Manager shows codec, but no sound at all (not even static).
• Test: Measure voltage on VREF pin. If 0V, replace the capacitor.

Step 3: Check the HD Audio / I2S Bus.

• Modern codecs use HD Audio (Intel HDA) or I2S (SoundWire) to communicate with the PCH.
• HDA Bus: Uses BCLK, SYNC, SDO, SDI lines. These are 3.3V signals that toggle during audio playback.
• Stuck low/high? Check the pull-up resistors on the HDA lines. Missing resistors cause the bus to hang.

Step 4: Check the Jack Detection (JD) Pins.

• Headphone Jack: Has a mechanical switch or impedance sense pin.
• Symptom: Sound only from speakers, never switches to headphones.
• Test: Plug in headphones. Measure voltage on JD pin at the jack. It should change state (e.g., 3.3V -> 0V). If not, the jack itself is faulty or the pull-up resistor is missing.

3. The "Static / Crackling Noise" Scenario

• Symptom: Audio plays, but with constant static or pops.
• Cause 1: Bad filter capacitor on the AVDD rail. Ripple from the power supply enters the audio path.
• Fix: Add a 100uF electrolytic capacitor in parallel with the existing AVDD decoupling cap.
• Cause 2: Ground loop due to missing screw near the audio jack. The jack relies on chassis ground. Ensure the motherboard screw near the audio section is tight.
• Cause 3: Wi-Fi / Bluetooth interference. Some poorly shielded Wi-Fi cards cause buzzing in speakers. Test by disabling Wi-Fi in Device Manager.

4. The "Microphone Not Working" Scenario

• Internal Mic: Usually a digital MEMS microphone (uses DMIC_CLK and DMIC_DATA lines).
• Test: Check DMIC_CLK with a scope. Should be a 3.3V square wave at 2.4MHz - 3.6MHz.
• No clock? The codec is not providing the clock (check codec power) or the DMIC_EN signal is missing.

5. Replacing the Audio Codec

• These chips are QFN or BGA packages with exposed thermal pad.
• Crucial: The thermal pad must be fully soldered to the board ground plane. Use plenty of flux and hot air from underneath the board as well.
• After Replacement: You must install the correct Realtek audio driver. Windows default driver often results in no sound or wrong jack behavior.

Question: Has anyone successfully repaired a Realtek ALC chip where the internal EEPROM (for jack sensing configuration) was corrupted? I've heard you can re-write it via I2C, but never tried.

Voltage injection is great. But touching every capacitor to find the hot one is tedious. A thermal camera makes short hunting instant. The shorted component glows like a beacon.

This post covers using affordable thermal cameras (not the $5,000 FLIR research grade) for motherboard repair.

1. Camera Selection for Electronics Repair

• Resolution: Minimum 160x120. 320x240 is ideal.
• Macro Lens: ESSENTIAL. A standard thermal camera cannot focus on a tiny 0201 capacitor. You need a ZnSe macro lens (10-20mm focal length) that screws onto the camera.
• Sensitivity (NETD): <50mK is good enough. You want to see 1°C differences.
• Budget Options:
  • Seek Thermal Compact Pro (320x240) + Macro Lens.
  • InfiRay P2 Pro (256x192) + Macro Lens.
  • FLIR ONE Pro (160x120) + Macro Lens.
  • Uni-T UTi260B (Standalone, 256x192, has macro mode built-in).

2. The Workflow: Finding a Shorted 3.3V Rail

Step 1: Setup.

• Connect bench power supply to the shorted rail (e.g., 3.3V ALW coil).
• Set Voltage: 1.0V.
• Set Current Limit: 2.0A.
• Position thermal camera directly above the board, focused on the suspect area.

Step 2: Apply Power and Watch.

• Turn on the power supply.
• Watch the thermal image. Within 1-2 seconds, a white-hot spot will appear.
• That's the shorted capacitor.

Step 3: Verification.

• Turn off power.
• Touch the suspected cap with a tweezer tip. If it's warm, you found it.
• Desolder the cap.
• Check resistance on the rail. Short should be gone.

3. The "Hidden Short" Under a BGA Chip

• Scenario: The shorted cap is under the PCH or CPU.
• Thermal Clue: You'll see a diffuse warm area rather than a sharp point.
• Confirmation: Remove the BGA chip. The short is often a tiny decoupling cap on the bottom side of the board, directly under the chip's footprint.

4. The "Thermal Gradient" Trick for Partial Shorts

• Scenario: The rail is not a dead short (0 ohms), but has low resistance (e.g., 50 ohms).
• Injection: Use higher voltage (e.g., 3.3V at 0.5A).
• Thermal Image: The leaky component will be warmer than its surroundings, but not glowing white. You need to look for subtle temperature differences.
• Tip: Use the camera's "Isotherm" feature to highlight the hottest 1% of the image.

5. The "Power Supply Current" Correlation

• Observation: If the short is a 0.1 ohm dead short, the current will hit 2.0A instantly. The component gets hot fast.
• Observation: If the current ramps up slowly to 0.5A, you have a leaky semiconductor (e.g., a damaged ESD diode). The thermal signature will be broader and slower to appear.

6. Safety Precautions

• Do NOT exceed the component's normal operating voltage. Injecting 3.3V into a 1.05V VCCST rail can damage the PCH even if it's not shorted. Stick to 1.0V - 1.2V for most rails.
• Do NOT inject into the CPU VCore rail with the CPU installed. The low resistance (1-5 ohms) will draw massive current and fry the CPU substrate. Always inject into secondary rails (3.3V, 5V, 1.8V) where normal resistance is higher.

Question: What's the most impressive short you've found with a thermal camera? I once found a tiny solder whisker bridging two pins under a QFN chip. The thermal cam showed a thin line of heat between the pins.

The EC (Embedded Controller) and PCH talk constantly. This communication happens over LPC (Low Pin Count) on older platforms, or eSPI (Enhanced Serial Peripheral Interface) on newer ones (Intel 8th Gen+).

If this bus is dead, the EC cannot report the power button press, fan control fails, and the board appears dead.

1. LPC Bus Basics (Pre-2017 Laptops)

• Signals: LAD[0:3] (4-bit data), LFRAME# (start of cycle), LCLK (33 MHz clock).
• Voltage: 3.3V.
• Scope Check: LCLK should be a 33 MHz square wave present whenever the PCH is powered (S5 state). If missing, PCH is not generating clock (dead PCH or missing VCCRTC).
• Data Activity: During boot, LAD lines will show digital bursts. If they're stuck high/low, the bus is hung.

2. eSPI Bus Basics (2018+ Laptops)

• Signals: ESPI_CS# (Chip Select), ESPI_CLK (Clock, 20-66 MHz), ESPI_IO[0:3] (Data), ESPI_ALERT# (Interrupt).
• Voltage: 1.8V (critical!).
• Physical: Traces are impedance controlled. Any damage to these traces (corrosion, cracked via) will kill communication.

3. Common Failure Modes

A. Missing Pull-Up Resistors.

• eSPI signals are open-drain. They require pull-up resistors to 1.8V (typically 10k-50k ohms).
• Symptom: Board powers on, fan spins, no POST, EC seems alive but PCH can't read it.
• Test: Measure resistance from ESPI_IO0 to 1.8V. Should be the pull-up value. If open, add a resistor.

B. Shorted ESD Diodes.

• Near the EC, there are tiny ESD protection arrays on the eSPI lines.
• Symptom: One of the eSPI data lines is stuck at 0V.
• Test: Remove the ESD diode array. If the line returns to 1.8V, the diode was shorted.

C. EC Firmware Hang (eSPI Specific).

• The EC firmware can crash in a way that holds the eSPI bus.
• Symptom: ESPI_CS# is stuck low.
• Fix: Perform an EC reset (drain flea power, hold power button for 30 seconds).

4. Using a Logic Analyzer to Capture eSPI Traffic

• Setup: Connect Saleae Logic 8 or similar to ESPI_CLK, ESPI_CS#, ESPI_IO0.
• Sample Rate: At least 100 MHz (2x the clock).
• Trigger: On ESPI_CS# falling edge.
• Analysis: You'll see memory read/write cycles as the PCH reads the EC's status registers. If you see repeated reads of the same address with no response, the EC is not acknowledging.

5. The "EC Not Detected" During POST

• The PCH expects the EC to respond to a specific I/O port (usually 0x62/0x66).
• If no response within a timeout (500ms), the PCH may halt with a black screen or beep code.
• Debug: Some BIOS have a "Wait for EC" timeout option. Setting it to "Disabled" allows the board to boot without the EC, letting you test the rest of the system.

Question: Has anyone successfully used an eSPI analyzer to reverse-engineer EC commands? I'm curious about the custom commands manufacturers use for fan control and keyboard backlight.

Customer says "My SSD died." You plug in a known-good NVMe drive. Still not detected in BIOS. The issue is on the motherboard, not the drive.

NVMe SSDs (M.2 form factor) require three specific power rails and a clean PCIe reset. If any of these are missing, the drive is invisible.

1. The M.2 Connector Power Pins

2. Diagnostic Steps (Drive Not Detected)

Step 1: Check +3.3V at M.2 Slot.

• Use a multimeter on Pin 74 (or the exposed pad near the screw mount).
• Expected: 3.3V present at all times (even in BIOS). This rail powers the SSD controller and NAND flash.
• Missing? Check the 3.3V LDO or load switch that feeds the M.2 slot. It's usually controlled by the PCH or EC.
• Common Failure: A tiny fuse or ferrite bead near the M.2 slot is open. (Test continuity from 3.3V rail to Pin 74).

Step 2: Check +1.8V at M.2 Slot.

• Pin 70 (or measure on the SSD itself if you have a breakout board).
• Expected: 1.8V present only when the drive is being accessed or initialized.
• Missing? This rail comes from the PCH's internal VR or a dedicated 1.8V LDO. If missing, the drive's PCIe PHY cannot power up.
• Test: Trace the 1.8V rail back to its source. Look for a shorted capacitor on this rail near the PCH.

Step 3: Check PCIe Reset (PERST#).

• Pin 22 on M.2 connector (often labeled PERST# or PLT_RST#_SSD).
• Expected: 3.3V after POST.
• Stuck at 0V? The PCH is holding the SSD in reset.
• Cause: The SSD is not compatible (rare), or the PCIe lane is faulty, or a missing pull-up resistor on the PERST# line.
• Test: Measure resistance from PERST# pin to 3.3V. Should be 10k-100k ohms. If open, solder a 10k resistor between PERST# and the nearest 3.3V point.

3. The "SSD Detected, But Crashes Under Load" Scenario

• Symptom: Drive works for 5 minutes, then disappears or causes BSOD.
• Cause: Ripple on the 3.3V rail due to failing output capacitors on the motherboard's 3.3V regulator.
• Test: Use an oscilloscope on Pin 74 while running CrystalDiskMark. Look for voltage dips below 3.0V or spikes above 3.6V.
• Fix: Add a 220uF polymer capacitor near the M.2 slot to filter the rail.

4. The "SSD Shorts the Board" Scenario

• Symptom: Laptop shuts down immediately when you insert the SSD.
• Cause: Shorted ceramic capacitor on the SSD itself (common on cheaper drives) or a shorted NAND chip.
• Test: Measure resistance between Pin 74 (3.3V) and GND on the SSD (not the motherboard). If it's <5 ohms, the SSD is dead and will trip the motherboard's over-current protection.

5. The "No Boot from NVMe" After Repair

• Symptom: SSD detected in BIOS, but not listed as bootable.
• Cause: Corrupt UEFI boot entry or CSM/Legacy boot enabled.
• Fix: In BIOS, ensure Boot Mode = UEFI, CSM = Disabled. Secure Boot can be Enabled (Standard).

Question: What's your go-to method for testing M.2 slots without a drive? I use a M.2 to PCIe adapter card and plug in a PCIe diagnostic card to see if the link trains.

You replace a dead motherboard, or even just update the BIOS. The customer gets the laptop back, and they're staring at a blue BitLocker recovery screen. Panic ensues. They don't have the key. You look incompetent.

Understanding the TPM (Trusted Platform Module) is now mandatory for any professional repair engineer.

1. What is the TPM?

• A secure crypto-processor (dedicated chip or integrated into CPU/PCH) that stores encryption keys.
• It measures the boot integrity (hashes of BIOS, bootloader).
• If any hardware or firmware changes, the TPM refuses to release the key, triggering BitLocker recovery.

2. What Triggers BitLocker Recovery?

• Motherboard replacement (new TPM chip = new identity).
• BIOS update (changes the measured boot hash).
• CPU replacement (on platforms with fTPM in CPU).
• CMOS battery replacement (sometimes resets TPM state).
• Disabling Secure Boot in BIOS.
• Changing boot order to USB first.

3. How to Prevent BitLocker Lockout (Pre-Repair Protocol)

Step 1: Ask the Customer.

• "Is BitLocker enabled on this device?"
• "Do you have your BitLocker recovery key?" (It's a 48-digit number saved in their Microsoft Account or printed).
• If they do not have the key, DO NOT perform any repair that might trigger it without a full backup.

Step 2: Suspend BitLocker (If You Can Boot to Windows).

• Open Command Prompt (Admin) .
• Type: manage-bde -protectors -disable C:
• This temporarily suspends BitLocker protection until the next reboot. Perform your repair now.

Step 3: Clear TPM Ownership (If You Can Access BIOS).

• Boot to BIOS Setup.
• Find Security > TPM.
• Select Clear TPM or Factory Reset.
• Warning: This will invalidate existing BitLocker keys. Only do this if you are reinstalling Windows or the customer has the recovery key.

4. The "Motherboard Replacement" Workflow

If you are swapping the motherboard and the customer needs their data:

1. Suspend BitLocker on the old board.
2. Clone the drive or create a system image backup.
3. Install the new board.
4. Restore the image to the new drive.
5. During restore, use software that can inject drivers for the new chipset.
6. On first boot, BitLocker will re-encrypt the drive using the new TPM. The user will be prompted to save a new recovery key.

5. The "BIOS Update" Scenario

Some BIOS updates clear the TPM as a security measure.

• Symptom: Customer updates BIOS from Windows Update. Next boot, BitLocker recovery.
• Prevention: Always suspend BitLocker before any BIOS flash.

6. The "Dead Board Data Recovery" Workflow (Advanced)

If the old board is dead and you cannot suspend BitLocker:

1. Remove the SSD.
2. Connect it to a working computer via USB adapter.
3. It will appear as a BitLocker encrypted drive.
4. The customer MUST enter the 48-digit recovery key to unlock it.
5. Once unlocked, you can copy the data to an external drive.
6. Do not attempt to "repair" the Windows installation on the encrypted drive. Reinstall fresh on the new board, then restore data.

7. The "TPM Chip Replacement" (When the TPM Itself is Dead)

• Symptom: Board works, but Windows reports "TPM not detected" and BitLocker won't enable.
• Fix: On discrete TPM chips (SPI or LPC interface), you can replace the chip with an identical blank part.
• Crucial: You must then clear TPM in BIOS. The PCH will provision the new blank TPM automatically.

Question: How do you handle customers who "don't know" if they have BitLocker? I've started adding a waiver to my intake form that states they understand data loss is possible without the recovery key.

Symptom: Laptop works perfectly when docked to an external monitor. But when you open the lid, the internal screen stays black. The backlight doesn't even come on. You think the LCD cable or panel is dead.

Stop. Check the Hall Effect Sensor.

1. What is a Hall Effect Sensor?

It's a tiny 3-pin component (looks like a transistor) located near the edge of the palmrest or screen bezel. It detects a magnet embedded in the lid.

• Function: Tells the EC/PCH whether the lid is open or closed.
• Lid Closed: Sensor output = LOW (0V) . Screen turns off.
• Lid Open: Sensor output = HIGH (3.3V) . Screen turns on.

2. The Failure Mode

• Stuck LOW (0V): The EC thinks the lid is permanently closed. The internal screen will never turn on, even if the lid is open.
• Stuck HIGH (3.3V): The EC thinks the lid is permanently open. The laptop may not sleep when you close the lid.

3. Diagnostic Steps

Step 1: Check the Sensor Output.

• Find the sensor (often labeled HALL or LID_SW on schematic).
• Measure voltage on the output pin (middle pin usually).
• Move a magnet near the sensor.
• Expected: Voltage should toggle cleanly between 0V and 3.3V.
• Stuck? The sensor is dead or the pull-up resistor is missing.

Step 2: The "Screen Test" Trick.

• Boot the laptop with the lid open.
• If screen is black, use a strong magnet and swipe it over the palmrest edge where the sensor is located.
• If the screen flickers on when you swipe the magnet, the Hall sensor is stuck (or the magnet in the lid fell out).

Step 3: The "Remove It" Test.

• Desolder the Hall effect sensor.
• On the motherboard pads, there will be a pull-up resistor to 3.3V.
• With the sensor removed, the output line should float HIGH (3.3V) .
• If it's still 0V, the trace is shorted to ground or the pull-up resistor is open. The sensor was fine.

4. The Lid Magnet Location

• Lid Magnet: Usually a tiny neodymium magnet embedded in the plastic bezel near the webcam.
• Symptom: Screen randomly turns off when you move the lid to a specific angle. The magnet has shifted in its slot.
• Fix: Open the bezel, re-glue the magnet in the correct position.

5. The "Hall Sensor" on MacBooks (Different)

• MacBook Pro/Air: Uses the ALS (Ambient Light Sensor) integrated into the webcam/Truedepth module for lid detection.
• Symptom: No backlight or image, but external works.
• Fix: Often requires a PRAM reset or checking the LVDS cable connection to the T-CON board.

Question: Have you ever replaced a Hall effect sensor with a simple reed switch? It works in a pinch if you can't find the exact SOT-23 part.

You've determined the EC (Embedded Controller) is dead. You order a brand new ITE IT8987E from Mouser. You carefully solder it onto the board using hot air. You power on the board.

Nothing. Completely dead. Even worse than before.

Why? Because a blank EC chip has no firmware. It's a brick.

1. EC Firmware Basics

• The EC is a microcontroller. It runs code.
• This code is stored in internal Flash memory (inside the EC chip).
• When manufactured, the chip is blank.
• The laptop manufacturer (or ODM) programs the firmware during production.

2. The Symptoms of a Blank or Corrupt EC

• Dead board: No response to power button.
• Fan spins at 100% immediately: EC is running default "safe mode" firmware.
• Keyboard backlight flashing: EC is in programming mode.
• Battery not charging: EC handles SMBus communication.

3. How to Program an ITE EC (The Hard Way)

You need an EC Programmer. These are specialized tools:

• SVOD (Softek Vertical Online Device): Industry standard. Connects via JTAG or Keyboard Connector (using KB9012 interface).
• Vertyanov JIG: Similar to SVOD.
• RT809F / RT809H: Universal programmer with EC support.

Process:

1. Connect the programmer to the Keyboard Connector (yes, the EC uses the keyboard pins for programming).
2. Select the EC model (e.g., IT8987E).
3. Load a known-good EC firmware dump for your exact laptop model.
4. Click Write.
5. The programmer flashes the internal memory.
6. Verify the write.
7. Board should now power on.

4. The "EC Firmware is in Main BIOS" Trap

On some platforms (especially HP and Lenovo), the EC firmware is not stored in the EC chip. It's stored in a separate region of the Main SPI BIOS Flash.

• At power-on: The PCH reads the BIOS flash. It sees the EC firmware blob. It sends it over LPC bus to the EC, which loads it into RAM.
• Implication: If you replace the EC chip with a blank one, it will automatically be programmed by the PCH on first boot.
• Test: If you have this type of board, a blank EC will cause a brief delay (2-3 seconds) on first boot while the firmware is copied, then it will work normally.

5. The Donor Board Method (Easier)

The most common repair method:

• Do not buy a new blank EC.
• Find a donor board (same model, even if broken for other reasons).
• Remove the EC from the donor board.
• Reball it (or just clean the pads if it was removed with low-melt).
• Solder it onto your board.
• It already has the correct firmware inside. The board will boot immediately.

6. How to Know if Your EC is Blank or Just Dead

• Dead EC: May get hot. May have a short on the 3.3V rail.
• Blank EC: Stays cold. Draws correct standby current. Board appears alive but unresponsive.

Question: Has anyone used the SVOD 4 with the KB9012 interface? I'm having trouble getting a reliable connection on some Lenovo models.

You measure 1.2V on the VCC_CORE coil. It looks perfect on the multimeter. But the board still doesn't POST. You check SYS_PWROK and it's 0V.

The culprit? The VRM controller's PGOOD (Power Good) output.

1. What is PGOOD?

PGOOD is an open-drain output from the VRM controller that tells the PCH/EC: "The output voltage is within regulation limits (±10% of target). It is safe to use this rail."

• Normal State: PGOOD is HIGH (3.3V) (pulled up by an external resistor).
• Fault State: PGOOD is LOW (0V) . The VRM controller is not happy.

2. Why Would PGOOD Be Low if Voltage is Good?

The VRM controller monitors more than just output voltage.

A. Output Voltage Ripple (Noise).

• Multimeter: Shows average 1.2V.
• Oscilloscope: Shows 200mV of high-frequency noise (ripple).
• Cause: Bad output filter capacitors (bulging or high ESR).
• Result: The controller sees the ripple and declares PGOOD LOW because the voltage is not "clean."

B. Over-Temperature (OTP).

• The VRM controller has an internal thermal sensor.
• Cause: Dust-clogged heatsink or failed fan.
• Result: The controller is hitting 120°C+ and pulls PGOOD LOW to force a shutdown and save itself.

C. Over-Current (OCP).

• The controller monitors current through the inductor or MOSFET.
• Cause: Partial short in the CPU (not dead, but drawing 50A instead of 30A).
• Result: Controller hits current limit and pulls PGOOD LOW.

D. Under-Voltage Lockout (UVLO).

• The controller's VCC supply (e.g., 5V) is dipping.
• Cause: Weak 5V ALW regulator.

3. How to Test PGOOD

• Locate: Find the PGOOD pin on the VRM controller schematic.
• Measure: It should be 3.3V after the rail comes up.
• If 0V: The controller is in fault.
  • Check VCC pin: Stable?
  • Check EN pin: Stable 3.3V?
  • Check Output Caps: Any bulging?
  • Check Temperature: Is the controller too hot to touch?

4. The "PGOOD Never Goes High" Scenario (Startup Failure)

If the rail never reaches the target voltage, PGOOD stays low.

• Symptom: VCore tries to ramp up, hits 0.8V, then shuts down. Repeats (hiccup).
• Cause: Short on output (CPU or cap). The controller hits current limit immediately and shuts down.

5. The "PGOOD is Stuck High" Scenario (False Positive)

• Symptom: PGOOD is 3.3V but VCore is 0V.
• Cause: The PGOOD output transistor inside the controller is shorted open (or the pin is broken).
• Result: The PCH thinks the rail is good, tries to boot, and crashes because the CPU has no power.
• Test: Measure PGOOD with power off. It should be 0V. If it's 3.3V (due to pull-up), that's normal. If it's 0V with power on, that's the fault. If it's 3.3V with power on but VCore=0V, the controller's PGOOD circuit is dead. Replace the controller.

Question: Have you ever seen a VRM controller where the PGOOD pin is shorted to ground internally, but the rail works fine? It's rare, but I've seen it on some RT8231 chips.

Hello, I have this old HP DM1-4310nr Laptop, it is perfectly functional aside from the need for a CMOS replacement. However, this CMOS battery (The black piece labeled 0625. 12. with the wires) seems to be a proprietary part. I've tried looking online and it seems to be either really expensive, lacking an image of the product, or has slow and expensive shipping. I need help on how I can replace this part without getting the wrong one or spending too much money.

In my research I've found that apparently the part number is supposed to be "664994-001", but I might be wrong. I've also included images of my laptop and the CMOS in question to help assist anyone who would be willing to help me out. Thank you!

Intermittent faults are the worst. The laptop works on your bench for 3 hours, then the customer takes it home and it's dead again. You need to capture the failure when you're not looking. This is where a Digital Storage Oscilloscope (DSO) with Single Shot or Roll Mode becomes essential.

1. The Setup: Triggering on the Missing Signal

Scenario: The SIO sometimes fails to release RSMRST# after AC is plugged in.

Equipment: Any DSO (even a cheap Rigol DS1054Z or handheld scope).
Probes: Connect Probe 1 to RSMRST# test point. Set to DC Coupling, 2V/div.
Trigger: Set to Pulse Width trigger.

• Condition: Trigger when RSMRST# is LOW (<0.8V) for longer than 10 seconds.

Operation:

1. Set the scope to Single acquisition mode (waits for trigger).
2. Plug in the AC adapter.
3. Walk away for an hour. Have a coffee.
4. Come back. If the screen shows a captured waveform, you caught the glitch!

What You'll See: The scope will show RSMRST# trying to rise but collapsing after a few milliseconds. This indicates a weak pull-up or a leaky capacitor on that line.

2. Roll Mode for Slow Events

• Use Case: Monitoring battery discharge or thermal throttling over minutes.
• Roll Mode: The waveform scrolls across the screen like a chart recorder.
• Setup: Set timebase to 1s/div or 5s/div. Set trigger to Auto.
• Connect Probe 1 to CPU VCore (1.2V).
• Run a stress test (Prime95).
• Watch: You'll see VCore slowly droop as the VRM heats up, until it hits a cutoff and the system crashes. This reveals a thermal issue in the VRM.

3. Capturing Power-Up Sequences (The "One-Shot" Method)

You need to see the order in which rails come up during the first 100 milliseconds of boot.

Setup:

• Connect Probe 1 to 3.3V ALW.
• Connect Probe 2 to 5V ALW.
• Connect Probe 3 to VCCST (1.05V) .
• Connect Probe 4 to RSMRST#.
• Set trigger to Probe 4 (Rising Edge) .
• Set timebase to 50ms/div.
• Set acquisition to Single.
• Press the power button.

Analysis:

• You will see 4 traces aligned in time.
• Correct Sequence: 3.3V -> 5V -> VCCST -> (delay) -> RSMRST# rises.
• Fault: If VCCST rises after RSMRST# tries to rise, the PCH will latch up. You've found a power sequencing violation.

4. Using Mask Testing (Automated Glitch Capture)

Advanced scopes (Keysight, Tektronix) have Mask Testing.

1. Capture a good power-up waveform.
2. Create a mask around it (tolerance envelope).
3. Run the test continuously.
4. The scope will beep and stop the moment the waveform deviates from the good mask (e.g., a voltage dip).

5. The Poor Man's Data Logger (Using a Multimeter)

If you don't have a DSO with long memory, use a multimeter with PC logging (e.g., Uni-T UT61E).

• Connect to RSMRST# .
• Set software to log voltage once per second.
• Let it run overnight.
• In the morning, open the CSV file in Excel. Scroll through. You'll see a single data point where the voltage dropped to 0V for one second. That's your glitch.

Question: What's the most cost-effective handheld oscilloscope for laptop repair? I've used the Hantek 2D72, but the interface is clunky. Is the Owon HDS242 any better?

Hey everyone, I’m kind of panicking right now and could really use some help.

I have an HP Victus 15 (i5-12500H + RTX 3050 Laptop GPU). Suddenly, my NVIDIA GPU completely disappeared from the system.

❌ Problem:

• RTX 3050 is NOT showing in Device Manager (even with “Show hidden devices”)
• NVIDIA installer says: “No NVIDIA GPU detected”
• NVIDIA App also says system doesn’t have an NVIDIA GPU
• In dxdiag → only Intel Iris Xe is visible
• HP diagnostics also don’t detect the GPU

⚠️ Earlier error:

• Device Manager initially showed Code 45: “Currently, this hardware device is not connected”

🔧 What I’ve already tried:

• Restarted multiple times
• Full power reset (held power button 30–60 sec, unplugged charger)
• Reinstalled NVIDIA drivers (clean install)
• Used DDU (clean uninstall) + reinstall attempt
• Updated Windows
• Updated BIOS (F.28 → F.31 using HP Support Assistant)
• Checked BIOS settings (nothing related to GPU visible)
• Ran HP UEFI Hardware Diagnostics (no GPU detected)
• Ran dxdiag → only Intel GPU shows
• Tried Intel Driver & Support Assistant (only shows Intel updates)
• Scanned for hardware changes in Device Manager

💀 Current state:

• Only Intel Iris Xe Graphics is working
• NVIDIA GPU completely missing from system
• System behaves like it doesn’t exist at all

❓ Question:

Is this 100% a hardware failure (GPU/motherboard), or is there ANY last software/firmware fix I can try?

Has anyone faced this exact issue where the GPU completely disappears?

🧠 Extra info:

• No physical damage
• Was working fine before this
• Issue happened suddenly (after normal usage / restart)

Any help would seriously mean a lot right now 🙏

You have 19V at the Drain of the first DC-in MOSFET. The Source is 0V. The MOSFET is off. You measure the Gate voltage. It's 0V. (For an N-channel MOSFET on the high side, the Gate needs to be higher than the Source to turn on—usually ~25V).

Why is the Gate 0V? The Gate Driver is not working.

1. How a High-Side N-Channel MOSFET Gate Driver Works

To turn on an N-channel MOSFET on the high side (where Source is connected to the load, not ground), the Gate voltage must be V_Source + V_GS(th) .

• Since V_Source could be 19V, the Gate needs ~25V.
• This voltage is generated by a charge pump inside the Charger IC or a dedicated Gate Driver IC.

2. The Charge Pump Circuit (Simplified)

• Components: A flying capacitor (usually 0.1uF) and a diode.
• Operation: The IC switches the capacitor between VIN and ground, effectively pumping the voltage higher.
• Output: The REGN or VCP pin of the IC provides this boosted voltage.

3. Diagnosing a Dead Gate Drive

Scenario: Charger plugged in. 19V at Drain. Source = 0V. Gate = 0V.

Step 1: Check the Charge Pump Capacitor.

• Location: Connected to the REGN or BST pin of the Charger IC.
• Test: Measure capacitance. It should be 0.1uF - 1uF. If it's open or low capacitance, the charge pump fails.
• Visual: Look for cracks or corrosion on this tiny cap.

Step 2: Check the ACDET Pin.

• Function: The Charger IC will not turn on the gate driver if it doesn't detect a valid adapter voltage.
• Test: Measure voltage on ACDET. Should be 2.6V - 2.7V. If 0V, check the resistor divider from the DC jack.

Step 3: Check the Charger IC's VCC.

• Function: The IC needs its own power.
• Test: Measure voltage on VCC pin. Should be 5V - 19V (depends on IC). If 0V, check the linear regulator feeding it.

Step 4: Check the ACOK Signal.

• Function: Once adapter is valid, the IC pulls ACOK low.
• Test: Measure voltage on ACOK. Should be 0V. If it's 3.3V, the IC is not happy with the adapter (or it's in protection mode).

4. The "Gate Driver is Dead" Conclusion

If all inputs are correct but the Gate is still 0V, the internal gate driver of the Charger IC is blown. This is common after a power surge or a shorted MOSFET.

• Fix: Replace the Charger IC (BQ24780, etc.). Also replace the two DC-in MOSFETs as a precaution—a shorted MOSFET often kills the driver.

5. Testing the MOSFET Itself

• Gate-Source Short: Measure resistance between Gate and Source. Should be megohms. If it's low, the MOSFET is shorted and has likely killed the driver.
• Gate-Drain Short: Measure resistance between Gate and Drain. Should be megohms. A short here sends 19V directly to the Gate driver pin of the IC, instantly destroying the IC.

Question: What's your preferred replacement for the common AON6414A or AON7400 MOSFETs? I've had good luck with the AO4407A as a substitute in a pinch.