PC-3000 Forum

Hello,
Connecting the Same To PC3K Gives The Following Terminal


Boot 0x80M DensityList:0x0000
PrgF
LED:0x000000BD FAddr:0x000059D8

LED:0x000000BD FAddr:0x000059D8

LED:0x000000BD FAddr:0x000059D8


This is Even Before The Spindle Motor starts Up ,But The Motor Does Not Spin Too ,Is This a Board Issue Or NAND Has Gone Kaput ,Any Procedure For Achieving Data Recovery

Hello Acelab staff ,
Do You Have any Way to solve ,I am Waiting for Your Teams Reply

For this moment PC3000 doesn´t support those drives. So you need to wait or to find another way to solve it.

k4z1 wrote:Source of the post For this moment PC3000 doesn´t support those drives. So you need to wait or to find another way to solve it.

Well,
They have solutions for everything ,But i am stunned i rarely get a response when i have a query,I have no idea why this is but its happening again and again .When We Help The Newbies Its Fine ,When we have a issue no response from any seniors ,staff

Anyways - > i Would say that if we transfer rom to a donor pcb it will spin for sure though i have never tried it ,But just like the kahuna we will need to init it in some way,Might be the next update is around and this update its there ,I have heard it is ,This is the reason i was asking staff to reply ,But its ok if this is what it is

Amarbir[CDR-Labs] wrote:Source of the post They have solutions for everything ,But i am stunned i rarely get a response when i have a query,I have no idea why this is but its happening again and again .When We Help The Newbies Its Fine ,When we have a issue no response from any seniors ,staff

Problem is that this forum is not for getting answers from Acelab staff, but for PC3K users to share their knowledge.
If you wan´t answers from Acelab it´s better to ask on technical support.

Anyways - > i Would say that if we transfer rom to a donor pcb it will spin for sure though i have never tried it ,But just like the kahuna we will need to init it in some way,Might be the next update is around and this update its there ,I have heard it is ,This is the reason i was asking staff to reply ,But its ok if this is what it is

It´s not that easy. As far as I know only few people can solve that issue.

k4z1 wrote:Source of the post

Amarbir[CDR-Labs] wrote:Source of the post They have solutions for everything ,But i am stunned i rarely get a response when i have a query,I have no idea why this is but its happening again and again .When We Help The Newbies Its Fine ,When we have a issue no response from any seniors ,staff

Problem is that this forum is not for getting answers from Acelab staff, but for PC3K users to share their knowledge.
If you wan´t answers from Acelab it´s better to ask on technical support.

Anyways - > i Would say that if we transfer rom to a donor pcb it will spin for sure though i have never tried it ,But just like the kahuna we will need to init it in some way,Might be the next update is around and this update its there ,I have heard it is ,This is the reason i was asking staff to reply ,But its ok if this is what it is

It´s not that easy. As far as I know only few people can solve that issue.

Well ,
I am a Very Experienced Engineer in Data Recovery ,I have Full Knowledge of Working Of Acelab And The Procedures They Follow

I got a case with same symptom, same log.

2TB Firecuda (ST2000LX001), Utility detects as Rosewood_8C in bootcode mode.

Have you figured out the case?

I saw you made a patched rom which is not working in another post, which utility did you use in your case?

k4z1 wrote:Source of the post For this moment PC3000 doesn´t support those drives. So you need to wait or to find another way to solve it.

Since that time nothing new happened.

The latest release is not gonna support it?

Do you know anyone else can do it?

SSHD Rosewood drives are unsupported by PC-3000 now.
There is no possibility to get firmware access.

ST1000LX015 is support pc3000 ?
is this drive Roswood_8C family ?

Just wanted to say - I have recovered a few ST1000LX015 (Rosewood 8C SSHD variant) & ST2000LX

The procedure is very simple indeed - disable the NAND by editing ROM, apply Tech unlock patch, assess/fix the SA/MC issues etc
If NAND is dead - replace with donor board and use NAND init (similar to Kahuna) - OR - the data can be accessed with the NAND disabled

It can be done by editing the IAP section in ROM

=================================================================================================================================


It's exactly as Paradog84 wrote above.

To turn off NAND (SSHD) you must:

1). Download the original ROM from the patient PCB,
2). Modify the patient's ROM - the flags (several bytes) in IAP segments (both copies) should be replaced "FF" values,
3). Next recalculate CRC for these segments (both copies) and write to ROM of donor PCB,
4). Mount the donor PCB to the patient's disk,
5). Next step - modify the ROM by TechUnlock patch - and we have access to the terminal,
6). For safety, make a full backup of the firmware,
7). Then we clean the NAND - by T>/OI command from the terminal level.

Power off/on and we have access to the data

Of course, this procedure applies to only NAND failure case.

Checked and done in cases ST2000LX001, ST1000LX015 and ST500LX025.

P.S. Modifications and CRC recalculation (of ROM) can be done using the F3ROMExplorer program (search via google - I used the version 1.0.9).


================================================================================================================================

What If desoldering NAND Chip off PCB ?
-spam it makes drive boot and access firmware and user data ?

O.S wrote:Source of the post What If desoldering NAND Chip off PCB ?
-spam it makes drive boot and access firmware and user data ?

have you tried it Sir?