[Help] Lenovo Yoga Slim 7-14ARE05 (DA0LS3MBAF0) – 25Q80DVN1G Flash Is All FF, USB-C PD Stuck at 5V

[m1ch43lzm]

Worth a try cutting the first 0x100000 (1048576 bytes) from the dump posted here, as it seems to repeat over and over
https://www.badcaps.net/forum/troubl...34#post1511939
Attached here

Schematics here: https://www.badcaps.net/forum/troubl...for-schematics

If the dump doesn't work, you can place your request here: https://www.badcaps.net/forum/troubl...-14are05/page2
Somebody with the same laptop may do a backup of that chip

[ekozeko333]

Worth a try cutting the first 0x100000 (1048576 bytes) from the dump posted here, as it seems to repeat over and over
https://www.badcaps.net/forum/troubl...34#post1511939
Attached here

Schematics here: https://www.badcaps.net/forum/troubl...for-schematics

If the dump doesn't work, you can place your request here: https://www.badcaps.net/forum/troubl...-14are05/page2
Somebody with the same laptop may do a backup of that chip

I tried the dump, it seems to cycle 20V -0V .. same.

[ekozeko333]

Little update...

in desparation started to measure every single cap.

I found a short on this line. I cant trace it to see where it goes, currently I dont have a adjustable power supply or a thermal camera to trace it.
Does somebody have a idea?

[m1ch43lzm]

That's the audio codec, probably some caps between AGND (analog/audio GND) and "regular" GND, both are supposed to be "shorted" somewhere, nothing to worry about

[ekozeko333]

That's the audio codec, probably some caps between AGND (analog/audio GND) and "regular" GND, both are supposed to be "shorted" somewhere, nothing to worry about

Thanks I was losing my mind last night at 2 AM..
Then its most likely the PDI Flash that needs to be truly configured.

somebody with much more experience can tell.

What I can tell is that I`ve tried To unsoled the TPS and try. I get 5v only.

With TPS soldered it negotiates to 20V-0V in cycle.

No shorts found anywhere.

With the NX20P5090UKAZ unsoldered I get 20V constant but it doesnt turn on to pass VBUS --> VINT

Initially the NX20P5090UKAZ was shorted and burned.
THE SPI Flash was corrupted not shorted ( defect internal ) .

[m1ch43lzm]

There's two of those NX20P5090UK, one for each USB-C port, check both
The TPS65988DJ controls both load switches, it's supposed to receive an "ACK" signal (low) when the switch is conducting

Datasheet of the NX20P5090 https://www.nxp.com/docs/en/data-sheet/NX20P5090.pdf


The ACK signals go to GPIO1 and GPIO2 for each port, have to check the Thinkpad L13 Yoga schematics (where the dump I linked came from)
https://www.badcaps.net/forum/troubl...tic-needed-pls

On the Thinkpad Yoga L13, GPIO1 and GPIO2 of the TPS65988 have pulldown resistors, on your board (page 31 of the schematics) GPIO1 and GPIO2 have 10K pullup resistors to LDO_3V3 (internal LDO of the TPS65988DJ); so probably it isn't expecting that with its current firmware and causes the "looping"
But at least with the current firmware it's negotiating 20V with the charger... (with that switch removed from the board)

GPIO16 and GPIO17 (active low) control the load switches on your board, on the Thinkpad Yoga L13 those GPIOs control some MOSFETs that allow the 20V to pass to VIN; different circuits that basically do the same thing which is to pass the 20V from USB-C to the input of the charge circuit
Page 41 of the Thinkpad L13 Yoga, and pages 32,35 of your board schematics

Check the MOSFETs at page 35, PQ13 and PQ17, measure in resistance mode S-D, S-G, D-G

[ekozeko333]

Thank you for the reply.

I know there are two of the NX20P5090.

Ive tested the whole board for short circuits including the PQ13 and PQ17. no shorts there. all is ok.

Ive did a whole analysis of the PD negotiation uncluding D+ and D- with and without battery on both ports. These are the Pictures attached.

Summary of PD Negotiation Behavior (based on 4 pictures checked):

• Port 1 (no battery):
  VBUS cycles between ~2.3V and 20V (short cycles), current ranges 0.007A – 0.045A.
• Port 1 (with battery):
  Longer cycles, VBUS 0V – 20V, current 0.00A – 0.025A.
• Port 2 (no battery):
  VBUS cycles ~2.3V – 15V (short cycles), current 0.007A – 0.040A.
• Port 2 (with battery):
  Longer cycles, VBUS 0V – 15V, current 0.00A – 0.025A.
• FNIRSI C1 shows PD cycling through protocols without settling — likely due to negotiation failure, proprietary protocols or measurement limits.

I attached also another working laptops pd negotiation for refrence.

EDIT: just want to add here that the CURRENT with other FIrmwares was 3A on 5V .. CPU GETTING SUPER HOT.

Its 90% likely a TPS firmware thing here were talking about. I wish someone could dump the exact same TPS from this exactly same motherboard. and even still I dont know if that is enough or something else needs fixing for the tps to talk to the ECU.

[ekozeko333]

I ordered a cheap logic analyser to attach it to the GPIOS to see whats up. it will take a week or two to report back what happens on these pinouts.

This is my first laptop repair and I am learning along the way I might benefit from watching some advanced videos if someone could share something more in depth and tehnical about PD negotiation and signal analysing ?

Thank everybody for the feedback and If we fix this I will surely create a indepth tutorial on what happened how to avoid and how to fix it

[m1ch43lzm]

I tried to extract the BIOS update from Lenovo dmcn44ww.exe, first with Innoextract, then WinRAR on the WIN64.exe, after that "Majolica.fd" with andyp phoenixtool 2.73; it's the only tool I found that decompiles the Insyde BIOS update .fd into individual modiules, and found 2 interesting files
1EAE5997-6A9E-7541-AED4-57FD7BC3BC05_1614.ROM
A3187945-5B5E-44C8-B03B-64BAA9E95785_1616.ROM

I checked them with hex editor, and the header/structure matches the dump from the L13 Yoga but with some differences
Maybe one of them will work for you, both are 45KB, try filling the rest with FF FF .... until you reach 1MB, i'll attach them

[dokterpc]

Worth a try cutting the first 0x100000 (1048576 bytes) from the dump posted here, as it seems to repeat over and over
https://www.badcaps.net/forum/troubl...34#post1511939
Attached here

Schematics here: https://www.badcaps.net/forum/troubl...for-schematics

If the dump doesn't work, you can place your request here: https://www.badcaps.net/forum/troubl...-14are05/page2
Somebody with the same laptop may do a backup of that chip

Thanks it's work on my latitude 7210 la-j321p, the tps65988 short on 1,8v and i change but stuck in 5V VIN, i try flash the firmware with this and it's work on 20V VIN. Thankss

[m1ch43lzm]

That's interesting, a dump from a Lenovo laptop worked on your Dell to get 20V
But according to the schematics for the LA-J321P the GPIOs control different stuff: GPIO1 and GPIO2 control a mux that routes the USB2.0 data lines on one of the USB-C ports according to cable orientation

Best to get the proper dump for your laptop for full functionality, it may be packaged with the BIOS update or the Thunderbolt controller firmware update
https://www.dell.com/support/home/en...-2-in-1-laptop

According to your schematics, UT6 is the PD controller flash, UT7 is the thunderbolt controller flash, it depends whether both UT6 and UT7 are fitted on your board

[SMDFlea]

That's interesting, a dump from a Lenovo laptop worked on your Dell to get 20V
But according to the schematics for the LA-J321P the GPIOs control different stuff: GPIO1 and GPIO2 control a mux that routes the USB2.0 data lines on one of the USB-C ports according to cable orientation

Best to get the proper dump for your laptop for full functionality, it may be packaged with the BIOS update or the Thunderbolt controller firmware update
https://www.dell.com/support/home/en...-2-in-1-laptop

According to your schematics, UT6 is the PD controller flash, UT7 is the thunderbolt controller flash, it depends whether both UT6 and UT7 are fitted on your board

There is a PD update only (not full firmware) in the bios update package