HDD GURU FORUMS

Anyone ?

128GB Integral flash drives both NAND BGA-132

Controller : FC2279 BA7

First Drive
NAND : ACELW2201N38A-H

Second Drive
NAND : JKQXN38B2243-1002A

Neither chip will ID on PC3000 Flash VCC 2-3.6v Drops out with reset errors at 1.8v. Drive #2 is known good and working.

Ask question.
Show Chipgenius info from second drive.

From Drive #2

Without NAND - would need to reball if you need it with. Looks to be the same as result from drive #1.

============================================
Description: [E:]USB Mass Storage Device(NAND USB2DISK)
Device Type: Mass Storage Device

Protocal Version: USB 2.00
Current Speed: High Speed
Max Current: 100mA

USB Device ID: VID = FFFF PID = 1201

Device Revision: 0000

Manufacturer: NAND
Product Model: USB2DISK
Product Revision: 0.00

Controller Vendor: FirstChip
Controller Part-Number: FC1178BC

Tools on web: http://dl.mydigit.net/search/?type=all&q=FC1178BC

==========================

Ah, I thought that you not desolder chip from Drive #2. Anyway, I have feeling that memory chip could be 6th byte addressing.

Nand attached : These pcbs are so cheap and flimsy I'm having to replace the mask each time otherwise the chip skids all over the place.

Description: [E:]USB Mass Storage Device(VendorCo ProductCode)
Device Type: Mass Storage Device

Protocal Version: USB 2.00
Current Speed: High Speed
Max Current: 100mA

USB Device ID: VID = 346D PID = 5678
Serial Number: 6610641276322786643

Device Vendor: USB
Device Name: Disk 2.0
Device Revision: 0200

Manufacturer: VendorCo
Product Model: ProductCode
Product Revision: 2.00

Controller Vendor: FirstChip
Controller Part-Number: FC1178BC
Flash ID code: 89D3AC32C204 - Intel - 1CE/Single Channel [QLC] -> Total Capacity = 1GB

Tools on web: http://dl.mydigit.net/search/?type=all&q=FC1178BC


Possible Flash Part-Number
----------------------------
Unknown


Flash ID mapping table
----------------------------
[Channel 0] [Channel 1]
89D3AC32C204 --------
1A2B3C4DE5D4 --------
CB75EFCD188B --------
CB741A803C00 --------
89D3AC32C204 --------
BB007CB80102 --------
4F75EDBEA306 --------
55AA75C78BF5 --------



1GB - Fake ?

Edit : Not fake according to grc's validrive.

I have at past case with ID: ID: 89 d3 ac 32 c6 00 (it was solved) - it was 6th byte addressing chip. So here should be same. Chip have 128GB - but according to FC controller there is chance that it will be refurbished and not use all capacity.

Looks like you're right about the chip, after much persuasion I managed to get this from it. I'll return this as above my pay grade and pass on your details again. I leave this here so the next person doesn't waste time with Ace TS.

This is from drive #1 flash marking : ACELW2201N38A-H

===============
Flash ID code: 89D3AC32C600 - Intel - 1CE/Single Channel [QLC] -> Total Capacity = 1GB

Possible Flash Part-Number
----------------------------
Unknown


Flash ID mapping table
----------------------------
[Channel 0] [Channel 1]
89D3AC32C600 --------

Case should be recoverable. Not so easy, but possible. I think all TS give up such cases at this moment

Hi,
See this VNR Update -> https://rusolut.com/visual-nand-reconstructor-8-0/

Reading this NAND flash currently is not a problem, but it requires modified hardware and software. PC3K explained the data recovery method for FC1179 controllers on its support blog two years ago, but the cases presented were ideal scenarios. The reality is that if you follow the guidance on the blog, the success rate will drop as low as 5%. Currently, nobody has the capability to perfectly solve the majority of FC controllers. Some individuals may perform better to some extent, but that's about it. The challenges stem from poor flash quality, adaptive bad bits, varied ECC algorithms, adaptive XOR, intra-block page clipping, sector clipping, unusual block mixing modes, partial block loss leading to incomplete file systems... I don't believe I'm doing well in this aspect. Over the years, I've encountered many people claiming to excel in recovering FC controller cases, but after some exchanges, most of them are exaggerating, and in many aspects, they are even worse than me.

csava wrote:Reading this NAND flash currently is not a problem, but it requires modified hardware and software.

Which for me at least, means it's a problem. If the chip can't be read with commercial tools without mods to those tools it's not economically viable to recover. I saw Aces blog post - it starts having already read the chip. As I see it, it's a complex case all round, problem nand, problem controller - best left to the flash specialists I have enough problems .