It's (probably) because True Blue are too busy fighting off the rival dongle (JBKing), and now, they had to resort to shoving in more DRM (*cough* HDD erasure *cough*) in the hope that JBKing backs down from the dongle war, but however, JBKing (and some of its users) have managed (some say "apparently") to get the affected EBOOT fixes working flawlessly on the dongle (JBKing).
As for the official reason, nobody knows why, but considering the fact there have been release pauses when its rival dongle fights back, that might be the case.
The Following 4 Users Say Thank You to gDrive For This Useful Post:
Come one please just don't start with this again, i know that IT'S REALLY ANNOYING to have to wait for the eboots, but WE ALL KNOW, that this is going to take time....TIME, A LOT OF IT
The Following 3 Users Say Thank You to TatoVR For This Useful Post:
The jb-king customers are happy they manage to fix the erase Problem in 3 days .. The true blue customers are not..they haven't see anything since 19th of march..
Originally Posted by nextbike
I have a felling that we all are going to very happy soon.
I predict a crushing blow to the RESISTANCE
The jb-king customers are happy they manage to fix the erase Problem in 3 days .. The true blue customers are not..they haven't see anything since 19th of march..
Really no one knows yet how did they solve the problem of the HDD, although it is likely to have used the elusive and mysterious update v2.51 of TB, this is what I think I may be wrong then huh
WOAH! This actually hasn't been closed yet, you lucky guy!
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3
The Following 3 Users Say Thank You to PatrickBatman For This Useful Post:
Originally Posted by nextbike
