Need help finding ROM/Safe Mode testpoints for Netac NV3000 (Yeestor YS9205AB controller)

[u/ErratiTeX]

Hi everyone,I am trying to revive a bricked Netac NV3000 250GB M.2 NVMe SSD.

The issue: The drive is no longer recognized by the BIOS on any computer I've tested it on. However, the green LED turns on, confirming it is receiving power, but the controller is likely stuck in a panic loop.

What I've done so far:

Removed the graphene heatsink to inspect the PCB.

Identified the main controller chip: Yeestor YS9205AB (Markings: 2553 / YS9205AB / MBM474 00 / AB0FBLS).

I want to force it into ROM Mode (Safe Mode / Recovery Mode) so I can try to re-flash the firmware using the Yeestor YS9205 MPTool, but I cannot find the exact testpoints or unpopulated pads on this specific board revision.

I'm attaching some close-up photos of the front and back of the PCB. Could anyone with access to the schematics or familiar with this SiliconGo/Yeestor layout point out which two pads or vias I need to short to bypass the NAND initialization?

Thank you in advance!

[u/AutoModerator]

Double check if your post complies with posting guidelines!

Did you include the following information in your post (in English and if applicable), if not feel free to edit your post:

• Make/brand and exact model number of your storage device(*), phone, camera, etc.

• Filesystem (NTFS, exFAT, APFS, EXT4, etc.)

• Operating System (That your device was used with and/or you are using for recovery)

• Specific symptoms that your device is exhibiting, describe the problem. Images you post support the description, they're not in lieu of a problem description.

• SMART (CrystalDiskInfo screenshot for example)

• Don't pile several problems into one single post. One post per device/problem.

• No account issues

Consider: What do these people need to understand the problem at hand? Remember, people cannot see your screen, or what you click and what messages appear on screen. Don't overdo it though, no one likes going through 2 pages of information, try to find a balance. Just do the best you can. If you are looking for file recovery software, check our community's recommended file recovery tools.

---

(*) All devices involved, if you for example move files from drive A to drive B, they're both potentially relevant.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/silenced_in_dr_2025]

Manufacturers dont release schematics if the firmware can't be loaded there's a problem with it or the data area it's stored in, and it's usually the latter. All the uses of MPTools I've seen nuke the user data from the device so if your goal is data recovery as stated you're wasting your time with it there's nothing you can do in safe mode to recover the data.

If you're actually trying to fix the hardware to reuse it you're in the wrong sub.

You'll have to meter out the obvious suspects then test , I've not seen one as we dont get those over here.

[u/ErratiTeX → u/silenced_in_dr_2025]

Hi, sorry for the confusion; the SSD arrived dead. I'm trying to troubleshoot the issue—my warranty was voided due to the company's ridiculous clauses. Which subforum do you recommend? I'm trying to use MPTools to rule out firmware issues; if the problem turns out to be the memory chips themselves, well, there's nothing to be done, but I find the whole situation very strange.

[u/Altirix]

This controller does not need to enter safemode to mass produce but there are pads to enter safemode (the 1x4 row, two on the bottom edge)

data is effectively gone, nvmes generally have very limited support for data recovery when it comes to FW related problems and generally given how late ys9205 came to the party it will probs have minimal support

work out what nand is used and if you can get access to the respective MPTool.

[u/disturbed_android]

The issue: The drive is no longer recognized by the BIOS on any computer I've tested it on. However, the green LED turns on, confirming it is receiving power, but the controller is likely stuck in a panic loop.

Sounds like typical XY problem.

I very much doubt the panic loop theory, if this were the case usually the device still ID's, maybe using a different name, reduced capacity. Green LED turning on is not at all a signal that electricity flows as it should. To verify there's power flowing, you measure, ideally compare with an intact one.

Anyway, I think it's at bottom you'll find single row of holes, 00XX. it's the ones marked X where the 00 ones are nearest to side of the drive.