Search results

Reclaime and updated UFS explorer can support BTRFS. Maybe there are more options, but these are the two I use for this FS

block SA regions, load LDR externally, load DIR from SA, check SA modules for errors. If you cannot find suitable LDR, then try hotswap to read #11 over composite read. Check SA address in ROM and ensure donor corresponds to it should you try hotswap

Potentially, depending on the model of passport, the wipe may have been a Cryptographic erasure, in which encryption key is erased and new one created to correspond with the new format. Generally a quick format will overwrite the first 256 MFT records (depending on the OS it was formatted in)...

short read channels to allow T> at terminal, edit 0x93 to remove any pending, reallocation and media cache properties, repower hdd Might be useful to post a log here...

I have 4 of these in total. So simple to use, especially since we have many users, both experienced and inexperienced with soldering. The problem I find with this is the lack of support from Acelab for a number of monolith devices which renders the adapter useless in many cases, unless a...

After learning VNR and seeing exactly what is involved in reconstructing flash devices, it does make you appreciate the things FE does and how simple it makes it look. Personally, I think Sergei is a genius 8-)

Do you have ISP pinmap for S6/S7 Note5 (with UFS chips)?

Terminal commands wont be possible on this. How does it look in hex, is it full of data? Scan in r-studio and watch the scan progress to be sure metadata and/or file headers are identified. If yes, leave a scan persist to try to identify a valid result with data. If no file headers are...

Did you try translator regen? Maybe you can patch ROM to stop No Host error and to force DRDY status then enter in eslip mode after regen translator. Can you read sectors like this?

Boot it from BIOS at an older PC with IDE connection, boot hirens Boot CD with MEdia Tools installed, clone to a new drive or recover to FAT32 formatted destination.

Look at results of your scan, choose some random files and view them with a hex viewer. Probably the files contain the wrong data meaning either metadata like file records are damaged or files have been written to with new data. Depending how much data was written with the factory restore you...

LED:CC means there is problem with translator or overlays, LED:EE is usually representative of some media cache error, Once you reach ready you should try to edit the SMP module. If you have PC3000 (or similar) you should be able to edit it with 'Edit HDD ID (Terminal) to disable reallocation...

System file 3_346_0 needs to be cleared or replaced.

WD drives are already more complex since families like Diablo and Shrek. Even restoring data without original ROM is near impossible on models such as Shrek due to extra Servo tables in ROM. I am starting to prefer Seagate over WD already :shock:

I wrote a case study about this when I first had one, and model alone is not enough for conversion to SATA. Ill send it over to you by email monday so you can look over it.

You need to autodetect key first from either some SA module (25 = initio / Jmicron / SED or 38 = Symwave) or from 'magic' sector at HDD. Did you detect key? Also, you need to ensure 'Deryption' box is selected

Did you disable reallocation and pending activites?

Perform a signature based scan (RAW recovery) just to test files. If RAW files are good, then data is not encrypted.

MCU and Motor controller should match, if not after conversion heads will knock and drive cant come ready. For example, 88i9317-RA12 (MCU) and ########### – TLS2602 should be the same.

This is not Initio 1607E chip, at your USB3 will probably be INIC 3608 or some variant which is means your Initio USB3 is a SED capable drive. Traditional Initio (1607E) like your case, will only be present on USB2 bridge only.

Initio will be on USB2 bridge, Symwave should be on USB3 bridge

What is the model? It may be easier to get in a SATA variant that you can use the PCB from.

What file system is it? File systems like EXT and NTFS have filesystem 'counters' you can use that may help. Also, in some nested arrays the block size of the top level stripe is the total number of sectors in a single stripe of data the RAID5 (excluding the parity block of XOR). At 64KB RAID5...

Maybe someone can send one to you? Since the Acelab update which allows live decryption from passport/mybook devices I imagine for a lot of people these adaptors are redundant. I can check Monday if I have one, but I cant check until then. Maybe someone closer to you has one they can send to...

What I mean is that XOR will be physically present at 2 disks at any time, but not within the same RAID5 set, so identifying the pairs of disks with XOR patterns at the same offsets will confirm they are from opposing RAID5 sets within the top level RAID0.

Let me know if you need any help with it, I can look at it remotely if you cant figure it out. You need to identify where the parity blocks are at each drive to work out the direction and length of it, also you can identify 2 disks with XOR at the same position then these are from opposing RAID...

Oxford are the enclosures with Firewire Bridge. There is no mention of Oxford in that post because not all Oxford cases have a copy of the key at the surface or even in the SA. Key is present in ROM of the bridge only. Here I have a copy of an Oxford key should it be useful for somebody.

Unless its Oxford encrypted, most Oxford cases do not have copy of key in the drive, but your image looks like encrypted MBR so it should be ok. Search in Winhex for string '57' at offset '0' from the end of the drive in reverse, post the key it finds and we can tell you which bridge you will...

Load LDR and search for SA modules. But something to consider is the region address. I have 2 x cases here with FW version of 00200049 and both have an address of '0' for the first region in ROM. I can send to you LDR if you need for this version.

It could be something quite simple to diagnose, but as PCLab said, we would need to see output from terminal.

Does it read at this speed at all heads? Also, did you take JAred advice and check the status if the 'HDD ID' options?

I always assumed they would offer encryption by default, even more so since I never saw one that had absolutely no encryption present. I always aim to learn something new everyday, I guess this counts :D

Encryption is made internally so it is irrelevant which interface it is read through as the bridge is not responsible for it. The model in this case is Shrek LT and should a secure format be made via Smartware utility it will render all current data unrecoverable because of change in key...

Did you ever manage to restore data from the lost partition? You can use Microsofts Repair BDE tool for such a situations. https://technet.microsoft.com/en-us/lib ... 29851.aspx

They are encrypted, but encryption is not done at the USB bridge, it is done at processor level. Data sent to the HDD is encrypted by controller and stored in encrypted form, but when read it is decrypted by processor and displayed in non-encrypted form. This way is simple for secure erasure by...

I would not be surprised if it is some 'fake' drive. I have had a lot lately. This week I recieved a 500GB WD with label 'WD5000BEVT-00A0RT0', but identified as Zephyr and had map of '0,1,2'. Entered the SN at Western Digital RMA check at website and confirmed it should actually be...

https://www.dropbox.com/s/aszd8kxvfwn0g ... P.pcr?dl=0 SA tracks, ROM and SA modules in PCR file.

The second ABA range you are writing to represents copy '1' of the SA modules. I usually relocate into the same copy but shorten length of some non important module like 'E0' which is a large module then use the now free space as the location for my bad module to reside. I have never relocated...

Do you have some resource of the same revision? Try an offline start using mod 01 from donor with same FW version. This is what I would try first. Without 02 or 11 drive will not come online alone, I would guess that dir module has some damage. After load LDR and search for SA modules, can you...

When I started working with flash it took two of us to take it on, I took the Soft Center route while my colleague took on PC3000. I was pretty lucky in that I had a few guys at skype that gave me good advice and support. I worked on flash alone for around 2 years, it really does require a lot...

For 21 (SMART) and 32(RELO) both can be written from donor, but what is common is the inability to write changes to these locations due to some surface reading error or bad sector at SA. Try to write from donor, then after writing if successful try to run relo fix to clear any donor relo...

Ill contact you at skype today and I can help you with it there.

the Kahuna series are usually hybrid sshd and can init from nand memory, if HDD has issues it can still initialise but data can't be read. if PCB is at fault and it is in fact sshd then PCB replacement will be extremely difficult as nand can contain information like rom and sa and is accessed...

Also, if you look inside module #C5 on any ROYL WD it will display the family identifier

This is Bigbear family. I only have 00060014 and 0003003T, have not seen many of these yet.

Do you have access to the SA? If yes, can you regenerate native ROM from mod #109?

I got to say, I do love all of the Slow Mo Guys videos :)

I recently work on a IDE Toshiba drive from a vehicle, we cloned it to a similar but not identical IDE Toshiba, then adjusted ID to correlate with the original. This worked well for the client. Not sure if this is helpful to you.

I think it depends on the family. If its a relatively 'old' ROYL like Pinnacle, Kermit etc then it should remain powered. For newer models, like Diablo, Shrek etc it may click. For pre-ROYL models it may click. In all models, if head map is different and does not match then it will click also.

This is ES.2. You should short it during calibration - at terminal window keep 'CTRL+Z' pressed as you power on, you will see a short window of time in which T> is possible. This is your time to short, usually during calibration. Once calibrated and SMART is cleared, repower it and it should be...

IT is defined at '0' but it is not recognized unless it is recognized under 'quick disk analysis' or if it is imported as virtual super-block when viewing in sector editor in DE. What meta-data is used for auto-detection? How is user data used for auto detection? Varied RAID controllers will...

I dont remember exactly, somewhere around 2,000EUR I think?

Yes, and in my opinion its pretty useless... auto-detect is poor, you really have to know the config before attempting to rebuild. Its more of a trial and error approach. When building RAID in XFS, XFS boot sector is usually sector 0 of the volume, but it doesnt access it because there is no...

Select 'Load LDR' and find an existing one in database (or download one, or make LDR from good donor). After LDR from database is selected next to App Code in dialog window that opens is a settings button. Press it and at the HEX view that opens right click select 'load from file' and select...

Pretty sure its media cache issue. You will need to find the right time to short. Probably just after calibration completes but before LED:BD error. Just as an extra measure, I always read ROM to verify it is native. Pretty sure yours is native based on how much of terminal looks normal though.

continued...

continued...

continued...

Here are a few RAID configurations from previous cases I have solved. With Reclaime providing a solution for finding RAID configs in addition to tools like UFS Explorer supporting MDADM based arrays, these configs may not be as useful as they once were, but in cases where parameters cannot be...

Ah, sorry... I was too eager in my reply and did not read your full post.. :? :)

All versions do. Select '512KB' then in the text box showing '512 KB' simply delete the 'K' and you have 512 B :-)

This is pending bug. You can usually solve by creating a loader. There is terminal command you can send to the drive but if there are any surface read errors and CERT does not rebuild then drive will be in worse condition. Can you save APP code from it and import to a loader? *At some older...

Try disable MC and auto relocation from system file 0x93

The terminal output looks normal, nothing obvious there. Sometimes these models will come ready after a prolonged state of BSY. If not, and you have no T> then you would need to make short circuit to retain T> to see what is going on with it.

There is no 500GB capacity inside the flash. It is a vendor programmable controller and it is actually some low capacity which loops its actual size repeatedly to emulate sectors that do not exist. Assuming it is 8GB stick, writing beyond this location will actually begin writing at the start of...

Case was repaired in teamviewer :)

Then the $Bitmap of media cache is bad and needs to be cleared.

for the last case I looked at there seemed to be blocks of metadata every 4472000 (ish) bytes, understanding this metadata and probably creating some tool or script would be needed to decipher it and allow building of the RAID. Also, analyzing the disks outside of the unit does somehow show...

On attempting to read ID do you see 'DWF' flag at status registers?

I know of only 3 people who say they can solve these without the unit, but have never had one built without the original housing. For me I have always required the unit. If the unit is faulty, its possible that the unit can be repaired, alternatively the disks can be entered into a donor unit of...

Check if PCB is original

R-Studio, Winhex, UFS Explorer PRO, PC3000 + DE = For me, these tools will cater reliably for 90% of jobs for me. I have not tried any of the software in the list because I cannot see that they would give any improvement over current software I have.

Most modern WD drives (but maybe not all) do not have a concentric alignment and its possible to remove platters individually without affecting issues such as alignment - practice against a non important but fully operational dummy drive to check it :D

SSHD are not properly supported in PC3000 and part of the repair process I use for Grenada SSHD a loader is required - unfortunately creation of a loader within PC3000 utility is impossible. Instead the overlays need to be manually loaded into an existing loader then saved to a new location...

I have a 30 page document containing a list of RAID controllers and a screenshot of the configuration used to recover. Sadly, I abandoned the project in late 2013 as I now use manual XOR tracing techniques to build and do not need these references anymore. But if they are useful to anyone I can...

Below are some common terminal outputs with the faults that are (generally) responsible for it: TCC-001A[0x000042F9][0x000042F9]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMM.... = This error relates to an inability to read Servo or Overlays. This message is also displayed...

I often see cases of Seagate where clients or previous DR shops have reconstructed the translator over terminal without preserving non resident list. Sometimes these can be resolved fully automatically via the Recover Translator in PC3000, sometimes it can be done partly automated and part...

Shasta USB have internal ROM.

This model is OK to work on, you just need to make sure donor is compatible.

For most cases, the status register will initially show BSY then all registers will go off. At this point a soft reset can sometimes give ready state. Alternatively, place patient PCB on a donor HDD and after some knocking it should come ready allowing access to CP

I think a big factor in cases with static friction where heads are stuck is how many times client tried to free it or continuous powering of it. Each attempt to power or unpark will 'tug' at the heads but the slider will be stuck to the media and all the forced attempts to get it going can...

Anybody tried this out yet? http://securityaffairs.co/wordpress/370 ... l-kit.html

You will sometimes find similar situation with some older 3.5" Hitachi and also on 2.5" Toshiba that knock heads for some time then reach DRDY condition. Obviously not a good idea to let a drive knock for so long, but in the right circumstances it can be beneficial :)

This is for Classic Seagate, not F3. What kind of commands would you want to know?

you can analyse the LVM info under Linux to get more info. For the X-RAID they implement for the most part a JBOD array with 1 dedicated disk for redundancy data that operates like XOR.

You may find it easier to read emmc via JTAG, though this depends on the condition of the hardware.

Sometimes there are errors within the file when reading, but its possible to read ignoring errors. The output file may have some unread blocks, but these can be patched and sometimes the file will write back. Seagate F3 do not have problem with checksum like WD so this is fine to do (though as I...

You should work with system files as opposed to modules. At any T> you can gain access to system files to create backup. Did you ever solve this?

Are you still working on this?