Lexar Professional CF CARD Compact Flash UDMA 7 Data Recovery

Zero Alpha offers professional data recovery for the Lexar Professional CF CARD Compact Flash UDMA 7. These high-speed Compact Flash cards are often used in professional cameras and recording equipment. Users may face issues such as file corruption, accidental deletion, or physical damage to the card. We accept mail in jobs from any location for recovery.

LEXAR Professional CF CARD 128 gb Compact Flash UDMA 7 data recovery.jpg

Lexar Professional CF CARD Compact Flash UDMA 7 Common Problems

  • Card not detected by camera or computer
  • Corrupted or inaccessible files
  • Accidental formatting or deletion
  • Physical connector damage
  • Controller or memory chip failure

LEXAR Professional CF CARD 128 gb Compact Flash UDMA 7 not working data recovery

LEXAR Professional CF Card 128GB Compact Flash UDMA 7 Professional Data Recovery Connector

Data Recovery Case Log

The LEXAR Professional CF Card 128GB Compact Flash UDMA 7 is a dependable storage medium that empowers photographers and videographers to capture and store their creative endeavors. However, even the most reliable technology can experience glitches, potentially putting valuable data at risk. The story of Zero Alpha Data Recovery's successful retrieval of photos and videos from an undetectable CF card serves as a testament to the importance of professional data recovery services.

In a world where memories are often captured digitally, the ability to recover lost data can be a lifesaver. This narrative underscores the significance of selecting reputable data recovery professionals equipped with the knowledge and tools necessary to navigate the complexities of modern storage media.

The customer said they were using the card and it downloaded about half the files when it suddenly failed. They plugged it back into the camera and could still see the photos but couldn't access them. They plugged it back into the reader and could no longer detect the CF card.

We were able to put the controller chip into safe mode by shorting the test points. The SM2236 is a 4-channel CompactFlash Card Controller.

Model : SM2236-AB
Serial : (03)5526888-20101108
Firmware : 
Capacity : 32 MB (65 520)

The silicon motion software can not detect this controller as its set via PATA and not USB.

SM2236G-AC CF memory card data recovery with BGA 152 Nand chips

sm2236g-ac lexar compact flash data recovery with 4 bga-152

Xor could not be found. Chip reading settings had to be corrected

[28.08.2023 20:25:04]: PinState ID=   8  -> 
[28.08.2023 20:25:04]: .. Bus= 8 bit/ IO0x-0 -> 
[28.08.2023 20:25:04]: BGA-152 Adapter mode: [Default] ID= 0x2C846454  (ID EXT= 0x2C846454 A9000000) - OK! Parts detect... 1 OK! 2 
[28.08.2023 20:25:06]: BGA-152 Adapter mode: [Default]OK! 3 
[28.08.2023 20:25:07]: BGA-152 Adapter mode: [Default]OK! 4 
[28.08.2023 20:25:08]: BGA-152 Adapter mode: [Default]OK! 5 
[28.08.2023 20:25:10]: BGA-152 Adapter mode: [Default]Not Found! 
[28.08.2023 20:25:13]: For current chip ID= ID= 0x2C846454  (ID EXT= 0x2C846454 A9000000) pinout scheme is  = 8. 
[28.08.2023 20:25:13]: Power Adaptert Parameters (VCC,VCCQ) will be get from chip database
[28.08.2023 20:25:13]: BGA-152 Adapter mode: [Default]
[28.08.2023 20:25:14]: Read ID for CE= 1 Bus = 1
[28.08.2023 20:25:14]: BGA-152 Adapter mode: [Default]
[28.08.2023 20:25:16]: Chip ID= 0x2C846454  (ID EXT= 0x2C846454 A9000000)
[28.08.2023 20:25:16]: BGA-152 Adapter mode: [Default]
[28.08.2023 20:25:17]: BGA-152 Adapter mode: [Default]
[28.08.2023 20:25:19]: BGA-152 Adapter mode: [Default]
[28.08.2023 20:25:20]: BGA-152 Adapter mode: [Default]
[28.08.2023 20:25:37]: Microchip ID =01 PATH =01:  
[28.08.2023 20:25:37]: Packet Size = 64 pages.  Microchip reading...
[28.08.2023 20:25:37]: ------------------------------------------------------------------
[28.08.2023 20:25:37]: Operation parameters
[28.08.2023 20:25:37]: Pin State....................: ID= 8 (TLGA-52)(Default (All are Z))
[28.08.2023 20:25:37]: States by pin..........(PIN):(STATE)
[28.08.2023 20:25:37]:                           01: -> Z
[28.08.2023 20:25:37]:                           02: -> Z
[28.08.2023 20:25:37]:                           03: -> Z
[28.08.2023 20:25:37]:                           11: -> Z
[28.08.2023 20:25:37]:                           20: -> Z
[28.08.2023 20:25:37]:                           21: -> Z
[28.08.2023 20:25:37]:                           22: -> Z
[28.08.2023 20:25:37]:                           23: -> Z
[28.08.2023 20:25:37]:                           24: -> Z
[28.08.2023 20:25:37]:                           26: -> Z
[28.08.2023 20:25:37]:                           27: -> Z
[28.08.2023 20:25:37]:                           28: -> Z
[28.08.2023 20:25:37]:                           33: -> Z
[28.08.2023 20:25:37]:                           34: -> Z
[28.08.2023 20:25:37]:                           35: -> Z
[28.08.2023 20:25:37]:                           38: -> Z
[28.08.2023 20:25:37]:                           39: -> Z
[28.08.2023 20:25:37]:                           40: -> Z
[28.08.2023 20:25:37]:                           45: -> Z
[28.08.2023 20:25:37]:                           46: -> Z
[28.08.2023 20:25:37]:                           47: -> Z
[28.08.2023 20:25:37]: Reading algorithm............: ID= 1: SDR
[28.08.2023 20:25:37]: Reading rule.................: ID= 1587(PLNS=1 PLN=2096/2096 BLK=512/512)
[28.08.2023 20:25:37]: Autoverification.............: NO
[28.08.2023 20:25:37]: Timings.....................:
[28.08.2023 20:25:37]:                           T1: 62.4 ns
[28.08.2023 20:25:37]:                           T2: 20.8 ns
[28.08.2023 20:25:37]:                         tREH: 83.2 ns
[28.08.2023 20:25:37]:                          tRP: 83.2 ns
[28.08.2023 20:25:37]:                  Full period: 166.4 ns. Max Speed 4 Mb/s (SDR!)
[28.08.2023 20:25:37]: --------------------------------------------------------
[28.08.2023 20:25:37]: Attention! Probably you need to use slow Read Mode
[28.08.2023 20:25:37]: (if big part of data is FF)
[28.08.2023 20:25:37]: It's recommended to use next timings: t1=6, t2=2, tREH=8
[28.08.2023 20:25:37]: --------------------------------------------------------
[28.08.2023 20:25:37]: Back analisys.............: NO
[28.08.2023 20:25:37]: Correct ECC...............: NO
[28.08.2023 20:25:37]: ------------------------------------------------------------------
[28.08.2023 20:25:37]: Power Adaptert Parameters (VCC,VCCQ) will be get from adapter settings
[28.08.2023 20:25:37]: BGA-152 Adapter mode: [Default]
Item count = 0
Item count = 0
[28.08.2023 21:24:38]:  Duration : 00:59:00 - OK!
[28.08.2023 21:24:38]: Microchip ID =01 PATH =02:  
[28.08.2023 21:24:38]: Packet Size = 32 pages.  Microchip reading...
[28.08.2023 21:24:38]: ------------------------------------------------------------------
[28.08.2023 21:24:38]: Operation parameters
[28.08.2023 21:24:38]: Pin State....................: ID= 8 (TLGA-52)(Default (All are Z))
[28.08.2023 21:24:38]: States by pin..........(PIN):(STATE)
[28.08.2023 21:24:38]:                           01: -> Z
[28.08.2023 21:24:38]:                           02: -> Z
[28.08.2023 21:24:38]:                           03: -> Z
[28.08.2023 21:24:38]:                           11: -> Z
[28.08.2023 21:24:38]:                           20: -> Z
[28.08.2023 21:24:38]:                           21: -> Z
[28.08.2023 21:24:38]:                           22: -> Z
[28.08.2023 21:24:38]:                           23: -> Z
[28.08.2023 21:24:38]:                           24: -> Z
[28.08.2023 21:24:38]:                           26: -> Z
[28.08.2023 21:24:38]:                           27: -> Z
[28.08.2023 21:24:38]:                           28: -> Z
[28.08.2023 21:24:38]:                           33: -> Z
[28.08.2023 21:24:38]:                           34: -> Z
[28.08.2023 21:24:38]:                           35: -> Z
[28.08.2023 21:24:38]:                           38: -> Z
[28.08.2023 21:24:38]:                           39: -> Z
[28.08.2023 21:24:38]:                           40: -> Z
[28.08.2023 21:24:38]:                           45: -> Z
[28.08.2023 21:24:38]:                           46: -> Z
[28.08.2023 21:24:38]:                           47: -> Z
[28.08.2023 21:24:38]: Reading algorithm............: ID= 1: SDR
[28.08.2023 21:24:38]: Reading rule.................: ID= 1587(PLNS=1 PLN=2096/2096 BLK=512/512)
[28.08.2023 21:24:38]: Autoverification.............: NO
[28.08.2023 21:24:38]: Timings.....................:
[28.08.2023 21:24:38]:                           T1: 62.4 ns
[28.08.2023 21:24:38]:                           T2: 20.8 ns
[28.08.2023 21:24:38]:                         tREH: 83.2 ns
[28.08.2023 21:24:38]:                          tRP: 83.2 ns
[28.08.2023 21:24:38]:                  Full period: 166.4 ns. Max Speed 4 Mb/s (SDR!)
[28.08.2023 21:24:38]: --------------------------------------------------------
[28.08.2023 21:24:38]: Attention! Probably you need to use slow Read Mode
[28.08.2023 21:24:38]: (if big part of data is FF)
[28.08.2023 21:24:38]: It's recommended to use next timings: t1=6, t2=2, tREH=8
[28.08.2023 21:24:38]: --------------------------------------------------------
[28.08.2023 21:24:38]: Back analisys.............: NO
[28.08.2023 21:24:38]: Correct ECC...............: NO
[28.08.2023 21:24:38]: ------------------------------------------------------------------
[28.08.2023 21:24:38]: Power Adaptert Parameters (VCC,VCCQ) will be get from adapter settings
[28.08.2023 21:24:38]: BGA-152 Adapter mode: [Default]
[28.08.2023 22:24:13]:  Duration : 00:59:35 - OK!
[28.08.2023 22:24:13]: Microchip ID =01 PATH =03:  
[28.08.2023 22:24:14]: Packet Size = 64 pages.  Microchip reading...

SM2236G DOUBLE XOR: ECC and Data

XOR has been found but this case is unusual for the SM2236G. In most cases like this we need only one XOR to solve it, but for this case we need two XORS. One for ECC correction and one for data assembly. Creating such XOR is not an easy task.