Right now it’s pretty much a brick but we hope someone can pick up where he left off and turn this work into something useful for others. That is until he tried a new command which ended up locking him out of the drive. He changed these values on the drive itself, and got pretty far. Once these values are changed in a binary file it is written to the drive at a specific location. In order to stand in for the original drive the new one must have the same model number, serial number, LBA, and firmware revision. started his quest by finding out what the program actually does. The tool that does this with WD drives is called HddHackr. set out to make his Seagate work in the Xbox 360, but his manual changes ended up bricking the drive because of just one little error. But if your new drive is a Seagate this tool will not work. There is a tool which will let you do it if you are using aWestern Digital drive as the replacement. If you’re looking to replace the hard drive in your Xbox 360 without just buying an official unit, you may be out of luck. Posted in Repair Hacks Tagged 7200.11, bug, busy state, firmware, hard drive, seagate Bricking A Seagate Drive While Trying To Make It Work In An Xbox 360 grabbed an Arduino instead, using it as a USB-ttl bridge. In the tutorial uses a serial-TTL converter. From there he issues serial commands to put it into Access Level 2, then removes the cardboard for the rest of the fix. This is necessary to boot the drive without it hanging due to the bug. The image in the lower right shows the drive with a piece of paper between the PCB and the connectors which control the head. put together the tutorial which illustrates the steps needed to unbrick the 7200.11 hard drive with the busy state bug. Some searching led him to a hardware fix for the problem. There’s a firmware upgrade available, but you have to apply it before the problem shows its face, otherwise you’re out of luck. It stopped working completely, and he later found out the firmware has a bug that makes the drive think it’s permanently in a busy state. But that turned out to be the problem with Seagate HDD which he was using in a RAID array. Hard drive firmware is about the last place you want to find a bug. Posted in Security Hacks Tagged ata, ATA security, hard drive, seagate Great work, and something that didn’t end up as a Hackaday Fail of the Week as originally expected. ‘we don’t know if this hard drive is yours so we can’t help you.’ It appears those code junkies didn’t know how to unlock a hard drive ether, so put all his tools up on GitHub. In going through a few forums, found a lot of people asking for help with the same problem, and a lot of replies saying. It turns out the password for the old drive was set to ‘0000’, an apparently highly secure password. He found his old password and used the same method to look for the password on the old, previously impenetrable drive. He then took another Seagate drive, locked it, dumped it, and analyzed the data coming from this new locked drive. Two hours and two Python scripts later, was able to dump the contents of his drive. By accessing the hard drive controller’s serial port, was able to see the first few lines of the memory and the buffer. Another Hackaday post proved to be more promising. After downloading the required tool, he found it only worked on WD hard drives, and not the Seagate sitting lifeless on his desk. originally found one of our posts regarding the ATA password lock on a hard drive. What followed is a walk down Hackaday posts from years ago. Hard drive gets shuffled around between a few ‘computer experts’ in an attempt to solve the problem, and eventually winds up on ’s workbench. Fast forward a few months, and the password is, of course, forgotten. Here’s a common story when it comes to password retrieval: guy sets up a PC, and being very security-conscious, puts a password on his Seagate hard drive.
0 Comments
Leave a Reply. |