Originally Posted by henry caine
ah yes i was confusing the dae.bin ap2.6 updates with the spring drive update but my point remains the same if u have ur drive key from from kmew 3.55 the when sony update the drive fw the 3key people can just reverse engineer it and u can use ur old dump key to sign it a new drive cfw no problem and if they can't well u can still play ur old back up games and play all legit games new or old on pass through mode and u will always have psn assuming this is safe for psn the only downside is no homebrew( a sacrifice i can personally make but i respect the opinions of those who cannot make that sacrifice)
so what is the prob this is essential the c4eva method except the cfw is on the 3key and not the drive itself u can update the drive and still have cfw on it using the 3key if a drive update didn't stop c4eva how can it stop xkey or 3key
As I have said before it doesn't matter if Sony can detect it or not. They will not let this go untouched. Sony can update the firmware therefor making it harder to crack if possible at all to crack. You like bringing up 360 so I will bring up a 360 drive. Look at the Hitachi drives capable of AP 2.5. LT 2.0 was severely delayed and LT 3.0 for that drive is still unseen. If you think Sony cant stop this will a little extra encryption on the drive then you are sadly mistaken. Just because the 360 can do it, doesn't mean the PS3 community can. I was also guilty of immediately thinking 360 when I first read about this, but this is a different beast with many unknowns. The way the key works is also very different compared to the 360. Also we dont have tools like dosflash or jungleflasher to help us. The PS3 doesnt have a standard sata port like 360 drives do. There is too little known to be able to guarantee that Sony cant stop this because they can if they really want to stop it.