December 28th, 2017, 20:49
December 28th, 2017, 21:41
December 28th, 2017, 21:55
December 29th, 2017, 0:51
pikus_09 wrote:Remember! My disk is my and is not for resale, and is empty!
December 29th, 2017, 7:13
December 29th, 2017, 7:42
December 29th, 2017, 16:49
Spildit wrote:Mega Important Case is not compatible with "fixing" a Seagate DM without any data for re-use.
You shouldn't be using that DM thing to start with. Just put it in the garbage bin and replace it with one HGST and be glad that it's damaged prior for placing data there !!!
December 29th, 2017, 17:55
December 29th, 2017, 18:08
December 29th, 2017, 19:31
December 29th, 2017, 23:59
December 30th, 2017, 3:36
Directory of F:\Seagate\Firmware\ST2000DM001-1CH164
SEABOO~2 RAR 17,164,859 12-30-17 6:19a SeaBoot_CC29_49.rar
TESTDE~1 LOG 1,090 07-29-13 8:07p Test Description.Barracuda-GrenadaBP-CC29_or_CC49.log
GPCC2949 CFS 432 07-30-13 5:32a GPCC2949.CFS
GBP1TB~1 LOD 1,733,632 07-30-13 5:32a GBP1TBCC49.LOD
GBP2TB~1 LOD 1,733,632 07-30-13 5:32a GBP2TBCC29.LOD
GBP3TB~1 LOD 1,733,632 07-30-13 5:32a GBP3TBCC29.LOD
GBP2TB~2 BIN 196,352 12-30-17 6:27a GBP2TBCC29_part_1_rom_22.bin
GBP2T~11 BIN 256 12-30-17 6:27a GBP2TBCC29_part_2_rom_1D.bin
GBP2TB~3 BIN 8,192 12-30-17 6:28a GBP2TBCC29_part_3.bin (same as part_10)
GBP2T~10 BIN 8,192 12-30-17 6:38a GBP2TBCC29_part_10.bin (same as part_3)
GBP2TB~5 BIN 40,896 12-30-17 6:36a GBP2TBCC29_part_5.bin (PK zipped?)
GBP2TB~9 BIN 917,544 12-30-17 6:29a GBP2TBCC29_part_4_mod_3D.bin
GBP2TB~6 BIN 65,536 12-30-17 6:38a GBP2TBCC29_part_8_ovly_00.bin
GBP2TB~8 BIN 65,536 12-30-17 6:38a GBP2TBCC29_part_9_ovly_01.bin
GBP2T~14 BIN 196,608 12-30-17 6:37a GBP2TBCC29_part_7_ovly_04.bin
GBP2TB~7 BIN 131,072 12-30-17 6:37a GBP2TBCC29_part_6_ovly_05.bin
GBP2TB~4 BIN 90,112 12-30-17 6:38a GBP2TBCC29_part_11_rom_sfw.bin
GBP2TB~1 BIN 4,352 12-30-17 6:39a GBP2TBCC29_part_12_rom_shell_copy1.bin
GBP2T~12 BIN 4,352 12-30-17 6:39a GBP2TBCC29_part_13_rom_shell_copy2.bin
December 30th, 2017, 8:19
fzabkar wrote:Let me see if I understand what happened.1/ You successfully applied Seagate's official CC29 firmware update.
2/ Then you wrote back your own drive's original CC24 sys files to the SA.
3/ Now your drive has its original CC24 SA and a new CC29 ROM.
If this is correct, then why can't you simply restore the CC24 ROM?
fzabkar wrote:I've extracted 13 component parts from GBP2TBCC29.LOD. I can't immediately identify parts 3, 5 and 10, but the others are ROM segments/containers, SA overlays, and SA module 0x3D.
- Code:
Directory of F:\Seagate\Firmware\ST2000DM001-1CH164
SEABOO~2 RAR 17,164,859 12-30-17 6:19a SeaBoot_CC29_49.rar
TESTDE~1 LOG 1,090 07-29-13 8:07p Test Description.Barracuda-GrenadaBP-CC29_or_CC49.log
GPCC2949 CFS 432 07-30-13 5:32a GPCC2949.CFS
GBP1TB~1 LOD 1,733,632 07-30-13 5:32a GBP1TBCC49.LOD
GBP2TB~1 LOD 1,733,632 07-30-13 5:32a GBP2TBCC29.LOD
GBP3TB~1 LOD 1,733,632 07-30-13 5:32a GBP3TBCC29.LOD
GBP2TB~2 BIN 196,352 12-30-17 6:27a GBP2TBCC29_part_1_rom_22.bin
GBP2T~11 BIN 256 12-30-17 6:27a GBP2TBCC29_part_2_rom_1D.bin
GBP2TB~3 BIN 8,192 12-30-17 6:28a GBP2TBCC29_part_3.bin (same as part_10)
GBP2T~10 BIN 8,192 12-30-17 6:38a GBP2TBCC29_part_10.bin (same as part_3)
GBP2TB~5 BIN 40,896 12-30-17 6:36a GBP2TBCC29_part_5.bin (PK zipped?)
GBP2TB~9 BIN 917,544 12-30-17 6:29a GBP2TBCC29_part_4_mod_3D.bin
GBP2TB~6 BIN 65,536 12-30-17 6:38a GBP2TBCC29_part_8_ovly_00.bin
GBP2TB~8 BIN 65,536 12-30-17 6:38a GBP2TBCC29_part_9_ovly_01.bin
GBP2T~14 BIN 196,608 12-30-17 6:37a GBP2TBCC29_part_7_ovly_04.bin
GBP2TB~7 BIN 131,072 12-30-17 6:37a GBP2TBCC29_part_6_ovly_05.bin
GBP2TB~4 BIN 90,112 12-30-17 6:38a GBP2TBCC29_part_11_rom_sfw.bin
GBP2TB~1 BIN 4,352 12-30-17 6:39a GBP2TBCC29_part_12_rom_shell_copy1.bin
GBP2T~12 BIN 4,352 12-30-17 6:39a GBP2TBCC29_part_13_rom_shell_copy2.bin
That said, I see that your drive's serial number is W24xxxxx, which suggests that it has 5 heads rather than 4. This in turn would suggest that Seagate's updater would have selected the GBP3TBCC29.LOD package (for drives with 3 platters).
Could you upload the CC24 and CC29 ROMs?
December 30th, 2017, 17:23
December 30th, 2017, 18:04
Spildit wrote:Did you try to write original ROM by terminal boot code mode ?
December 31st, 2017, 21:20
January 1st, 2018, 9:01
January 7th, 2018, 9:19
January 7th, 2018, 16:59
January 7th, 2018, 17:23
Powered by phpBB © phpBB Group.