[yoodog]

Hi,
have unusual case when CP lock will not be gone after normal process:
1. Bin file
2. v850 and reboot
3. delete Persistency - all 3 jobs and mid with SWT, reboot
4. flash to latest istep (0319 actually used)
5. check errors - CP still there (loading FSC and 170 doesn't help as it usually does)

Who has 0716 and 0718 on mega? 

PS: all 3 vins are changed and stored ok - CPS, Short, Long all changed
PSS: If you have any other idea please advice - I have only one more: load repair pack and see if it will remove CP, than change.

---

Another person sent me his patch and it didn't make any difference (that was back when unit was on 0318)

---

SSH is still open btw if any one fills like trying them self.
----------------------------------------------------------------------------------------------------------------
////////////////////////////////////////////////////////////////////////////////////////////////////////////////
----------------------------------------------------------------------------------------------------------------
Issue has been solved by removing Emulator from FEM bench - virgin reflash under FEM VIN - disabling CP lock completely with bin file- erasing FSC without removing patch - than doing reflash again without CP lock re activation - and applying HUtool FSC manually.

[HU_man]

Step 4 - flash with target FA (include 609), apply FSC patch and then import FSC 170 with that target VIN. CP will gone.

[yoodog]

Doesn't work, trust me I know how to make an fa hahah. How do you think I flash it otherwise with complete virgining  That is not the issue. All other FSC load accepted, but 170 rejects the second it Write, Check is done. Normally it should accept for few min, than go to reject = CP gone. 


That is not happening here for some f reason

Step 4 - flash with target FA (include 609) and import FSC 170 with that target VIN. CP will gone.

[FSCmap]

Is it used HW 4.1 unit?

[kubixix]

Is it used HW 4.1 unit?

Is there some problem with HW4.1 unit and removing Component Protection?
I am thinking about retrofitting one of these units.

[yoodog]

Is it used HW 4.1 unit?

Is there some problem with HW4.1 unit and removing Component Protection?
I am thinking about retrofitting one of these units.

Not really, just can falsh 4.1 with older than 1117 data (some people think it is 0318)

in terms of patching I only heard issues for Asian FSC

---

or Eng

Is it used HW 4.1 unit?

No it is 3.1 F series unit flashed, virgin and flashed to 03.19 - fsc don't work. Today virgin,tool32 3 jobs, flashed to 0318, but doesn't work again. (in this case I believe PSDZDATA is corrupted)

That is why im looking for latest PSDZDATA with 0718, I think it is around 4.15.33 + as back up if nothing works 0716 data which is around 3.59 if I'm not mistaken 

Odd shlt

[yoodog]

Issue has been solved by removing Emulator from FEM bench - virgin reflash under FEM VIN - disabling CP lock completely with bin file- erasing FSC without removing patch - than doing reflash again without CP lock re activation - and applying HUtool FSC manually.