If only "installer" not ignores it like root. ^^ Anyway, just an idea how to solve that issue in easy way (also easy to change by FTP client in case of need to delete).
in case of a repair, you only need to know where vflash? and devflash is located in dump and then just overwrite with garbage. PS3 will automatically ask for reinstall. this is how it works on NOR at least, so it should work as well.
edit
ok, discard the idea, cause we will never know on SS. maybe getting a SS now, and doing some bruteforcing, to get offset for devflash partition
For what reason? PS3 not using MBR partition table, nor the NTFS filesystem. If the goal is to make the disk unrecognized, it is pointless too because it will be unrecognized anyway as data cannot be decrypted from different console.
So as I said, PS3 will not recognize HDD logic structure from different PS3 because it is encrypted by different key than key which she using for decryption attempt. For that reason, it will always be empty drive for her until she format it, so she will use her keys, making in the process disk unrecognized on another PS3 from which this HDD came from. Exactly that's why writing anything on this HDD is pointless.
I saw some people saying the method, but I did not understand anything. Should I format the hard on Ntfs twice and return it to the device and download hfw and hen using usb, or download them from the computer and put the hard in the device
I think my ps3 eMMC is dead... Neither controllers are not connecting... Can I do something?? like re-install the fw. I am dumb . If it works, I wont re-exploit the ps3 again.... Model PS3 SuperSlim 12gb cech-42xxxxA
That wouldn't be news the whole chip is probably doomed other devices like wii u and galaxy tab 2 etc have mass emmc premature failure same model sony might have just used previous stock. probably the reason we never had more emmc base consoles.
only probable solution would be chip replacement but flasing partition table and dump is a dead end for now