If you have ever dealt with monolithic data recovery, you have definitely faced the necessity to find out the order of the bus line pins. Previously, if you had not known the order of the bus line pins and if you had no pinout map with all the information – such a case could not have been solved. But now things are easier with the new feature we showed at the ACE Lab Online Technology Conference 2021. From here on, with the Spider Board adapter and the latest PC-3000 Flash software update 7.5.11 you will be able to find out the order of the bus line pins!
Have you ever been in a situation when you were unable to finish the case with a complete file structure just because there was no Translator or Block number option for your particular case? It was a common issue for cases with such controllers as AU, SSS, FC (and some other ones, not that popular). But not anymore! With the latest PC-3000 Flash update Ver. 7.5.14, you can use a new assembling method for such cases, which carries out all the boring manual tasks automatically.
Last week we have discussed how to make the first steps in NAND Flash data recovery with the PC-3000 Flash during the ACE Lab Free Webinar. Following up, we have prepared for you this article about the vital procedures for recovering Flash cases. This topic will be especially interesting for beginners in NAND Flash data recovery who want to learn how to deal with NAND Flash in the most efficient and the smartest way. For already experienced data recovery specialists, this article can serve as a handy checklist on the main data correction methods while dealing with Flash cases.
Firstly, we are going to discuss ECC Correction and Rereading of invalid sectors.
FirstChip Technology started its expansion on the Flash market a few years ago. Today, some of the modern USB Flash drives are based on the FC1178/FC1179 controllers. Data recovery from most of these devices can be intricate because you may face 1-bit size bad columns, adaptive XORs, and very complex internal translations while working with them.
The good news is our developers have done a tremendous job in extracting XOR to add some of the FC1178/FC1179 controllers to the Support List. Now, you can recover data from even more NAND Flash devices! And, in this article, you will find the steps on how to do it.
Sometimes you may come along a Self-Encrypted Seagate drive that has a user password set by its owner. A common ‘Reset password‘ option doesn’t work because the option requires Power OFF/ON step, and the drive is SED locked.
How to deal with this case? Find the step by step procedure right in the article below.
Over the past years the PCIe interface has become very common in Solid State drives. However, until 2020 it was not possible to recover data from such damaged SSD devices. The PCIe lines inside the PC-3000 Portable III tool give you the ability to recover data and evidence from the PCIe SSDs along with the ATA-based devices. But it doesn’t stop here!
Our developers constantly add more drives to the SSD Support List. During the ACE Lab Online Technology Conference 2020 we have announced the Apple NVMe drives support. Now you can recover data from modern Apple-based SSDs with our new PCIe NVMe/AHCI Adapter for Apple Macbook SSD.
However, a number of Apple Macs, released between 2013 and 2016, were left unreached because they are based on the proprietary NON-NVMe architecture – the Apple AHCI PCIe protocol. So, this September we have released the beta version 6.8x of the PC-3000 Portable III. The update allows you to deal with all types of PCIe SSD drives, including the Apple AHCI ones that were hugely popular in the Macbooks, Mac Pro, and iMacs from 2013 and onwards.
Posted in Articles, PC-3000 SSD
Tagged AHCI, Apple SSD Recovery, Apple SSD, Apple NVMe, NVMe, PCI-E SSD, PCI-E x16 SSD, PCIe, Plextor, SSD
As you know, the PC-3000 Portable III supports the PCIe SSDs along with the SATA-based devices. Also, thanks to the new adapters and software updates, we constantly add new drives to the supported list. In September 2020, we have released the new PCIe x16 SSD Adapter for custom and native NVMe SSDs with PCIe x1-x16 interface.
It is extremely useful for drives that have a full-size PCIe bus as the only option of plugging in an SSD (e.g. Intel DC P4618 or Samsung PM1733). You may come upon such drives in server platforms and data centers because they are very stable and powerful. However, bad sectors can still appear due to prolonged use. In this case, the new PCIe x16 SSD Adapter paired with the PC-3000 Portable III System helps to bypass bad sectors and get the data from SSDs.
Posted in Articles, Data Extractor, PC-3000 SSD
Tagged Data Extractor, DE, NVMe, PC-3000, PCI-E, PCIe, Plextor, Portable III, SSD
The COB (Chip On Board) memory chips present a challenge to data recovery engineers trying to recover data from them. The main obstacles lie in their internal structure: under the coating of black plastic, there is just a NAND crystal with small traces connected to the PCB. The procedure of coating removal is very dangerous since you can easily damage the NAND core. And even if you succeed, it doesn’t mean that you can read data from such a chip.
So what can you do if a NAND Flash drive with the eMMC chip that has a disabled controller, the COB controller, or even the COB memory chip ends up on your desk? In this article, we will show you the unique way to handle these untypical but commonly encountered cases.
Posted in Articles, PC-3000 Flash
Tagged Chip, COB, Data Recovery, Flash, Flash data recovery, monolith, NAND, PC-3000, recovery, Spider Board
As you well know, our new PC-3000 Portable III tool has a built-in screen and it’s own Operating System, which allows communicating with connected drives without a host PC!
In this article, we are going to find out what features of the Standalone Mode are available to the owners of the PC-3000 Portable III.
Let’s imagine the following situation:
After you have finished recovering data, you get only a sequence of binary files which contains recovered raw data that were deleted or corrupted (e.g. task.prm, map.bin, and other files related to the task settings). Or, say, you have used some other tool for data imaging and got some sequence of binary data files as well.
What to do with this? Let’s find it out in our new article