Gigabyte Gen4 4000E 1TB PS5021-E21T UART pad ID after KB5063878 brick

Gigabyte Gen4 4000E 1TB (PS5021-E21T) bricked by Windows update - UART pad identification needed
Body:
Hello,
My Gigabyte Gen4 4000E 1TB SSD has been bricked after a Windows 11 bluescreen following the KB5063878 update. The drive is completely invisible — not detected in BIOS, not showing in Device Manager even as unknown device.
Drive details:
• Model: Gigabyte Gen4 4000E 1 TB
• Controller: Phison PS5021-E21T
• NAND: Micron QLC
• I do not need data recovery — I only want to revive the drive itself
What I have tried:
• Different M.2 slots
• Different PC
• Gigabyte Phison E16 reinitial tool (does not detect the drive)
• Drive is completely invisible to all software
Current situation:
The sticker has been removed. I can see the PCB clearly. There are three exposed pads on the top edge of the drive — two larger ones with circle silkscreen markings, and one smaller pad beside them. I am attaching a photo.
I believe these may be UART/debug pads based on the PS5021-E21T datasheet, which lists built-in UART and GPIO. Can anyone identify which pad is TX, RX, and GND so I can attempt firmware recovery?
Thank you
[img-0]

Program ( phison у7 flash id ) read SSD ?
or W.Oczkin ( phison nvme flash id2 ) ?

- If the update had a bug, you will not do anything

it read with 500GB SSD Gigabyte Gen4 4000E , ctrl PS5019-E19.



You need to find where in Phison (which pin's) are USART1_TX and USART1_RX ?
* You need to find where in Phison (which pin's)are USART1_TX and USART1_RXTX, RX

p.s
Link

!

Xplo5ding wrote:

was locked after Windows 11 bluescreen after KB5063878 update

- this is not a cause and effect relationship, but a coincidental coincidence. The real cause of failure is wear and tear on the memory chips by programming/deleting operations. Such situations are often unjustifiably associated with system updates, because a great deal of writing is done during them - downloading update files, extracting them, replacing existing system files with new ones, deleting redundant and temporary files...each of these operations is accompanied by operations on file system metadata - so crashes often occur during updates. But the real causes lie deeper:
https://kaleron.pl/SSD-failure.php

Xplo5ding wrote:

QLC

- let it go. Even if you succeed, the failure will happen again in a while.

>>21880476

I only used the drive for 6 months only….

Added after 57 [minutes]:

Thank you both. I understand the QLC wear point — I just want to revive the drive, I don’t need it to last long.
@lisek — Phison NVMe Flash ID2 does not detect the drive at all. The drive is completely invisible. I have attached a photo of the PCB showing 3 exposed pads on the top edge (2 larger with circle silkscreen markings, 1 smaller). Can you or anyone identify which are USART1_TX and USART1_RX?
I also received the usbdev.ru firmware link — is this the correct firmware for PS5021-E21T recovery?

this is the correct firmware to recover PS5021-E21T
- provided the drive is operational

Do you have power on the circuit board?
Controller PS5021-is it warm?
POd under Live Linux (e.g. Ubuntu) visible ?

p.s
Nowadays almost all new SSDs only have these 3 fields/points (UART)

So on one of them the power is both when the SSD is not specified and when it is specified.
But on the other only when the SSD is seen.

As the program ( W.Oczkin ( phison nvme flash id2 ) ) does not see it .... NOTHING you can do , dead controller

>>21880996 Update: I found the Phison E7 Flash ID tool, which mentions ROM mode via shorting contact holes near the retaining screw. I have measured the 3 pads:

Left pad: floating, no connection
Middle pad: 13.9 kΩ to ground
Right pad: confirmed GND (beeps to M.2 mount)

Which two pads should I short to enter ROM mode for PS5021-E21T?

Added after 48 [minutes]:

@Xplo5ding @lisek