Sediv free version is not able to load from loader, only generates it (which is the same of module 11).
Does WDR 6.0 able to load the loader?
How?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Maybe i understood what's wrong on head map...
If i push the button in the red circle, it counts only 1 head:


So i think it can't load SA because 5 heads are off or not counted in head map...
It makes sense for you?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Now if i push the button in red circle i get always 6,

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

No!

0,1,2,5,6,7 is valid head map for SadleG6 drives

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

Logical vs Physical

Not always the same

Typical 2Tb SadleG6 has physical 0,1,2,3,4,5 (i.e. all populated) but logical (ROM head map) 0,1,2,5,6,7

As a typical 500Gb Tornado have 2,3,4,5,6,7 in ROM, but 0,1 are not physically missing.

I have no idea how WDR (or whatever software he used) decides which is which for "de-popping".

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

In the pic you can see that i have depopped head 4 on "virtual head"


If rom head map is 0,1,2,5,6,7, what physical head has been turned off?
(maybe head 5)

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

It's a "Road Map error", i don't know how to fix it.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Yes Spildit, i restored with my eeprom programmer, nothing change.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

What should i do now?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

No it doesn't read, i get ~id0001.bad (0 byte) if i push "read"

P.S.
i copied the 01 module from my backup folder to WDR working folder, then i pushed "write" into w/o road map window.
Still i can't see modules.

P.S2
If i push once again "read" after i write 01 backup, i still get ~id0001.bad

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

i already "played" today afternoon with "Auto Good Map" and "Heads Map on", but i still can't see modules.
The only way i can see modules is when i do Road Map - Via enumeration, but i'm not able to read or write them

What can you tell me about "init" button on w/o roa Map?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Virtual head it's already set to 6

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

If one haead is off now (suppose one which reads the SA), why can't i read SA from the other head?
SA is on 2 heads (0+1), right?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

ok thanks, tomorrow i will ship the drive in rma

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Head depop writes also in some SA modules (WDR 3.0 works this way).
If you read my previous posts, when i did the head 1 depop, i couldn't turn on head 1 with only ROM restore (the drive was still identified as 1500 GB but modules were accessible), after i restored SA modules from backup the drive was again detect as 2 TB.
viewtopic.php?t=25749&f=1&start=120#p175449

Maybe head mapping change only ROM information, but head depop does also SA changes.
If i had made ​​the head map instead of the head Depop, maybe all of this would not have happened, but now ...

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

To 'depop' a head will change sizes of zones, which will make data recovery impossible. Change head map in RAM retains zone sizes, but if head other than SA head is set it wont read anyway, also for Sadle head map edit process in commercial tool is not same as older series.

I packed up the drive this morning, now i'm waiting the arrival of the courier.
Thank you every one who helped me and who gave explanations.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI