v2 TrueBlue CFW released (for downgraded consoles and for future updates)

[PatrickBatman]

We have released V2 of the True Blue PS3 custom firmware (CFW).

TB team:
This release adds the "no check" patches in order to support hardware downgraded consoles.

We recommend that all True Blue users update their PS3 to this CFW as soon as possible, as support for V1 CFW will be depreciated with the upcoming True Blue dongle firmware update.

MD5: ff689e1e8cdd02a46ddadb14c3c5b85c *PS3UPDAT.PUP



DOWNLOAD LINK: http://www.multiupload.com/C08L00RS7U

[nativesith]

Thank you for the update=). I think it should be stated that one must update from the recovery menu though. I have been having a few issues with 3.56 games, wonder if this update will help. Will those of us on the Rebug TB ed have issues?

[.Spike.]

Wow a useless update. That does nothing to improve it.

[Ps3funktionz]

Thank you for the update=). I think it should be stated that one must update from the recovery menu though. I have been having a few issues with 3.56 games, wonder if this update will help. Will those of us on the Rebug TB ed have issues?

You will most likely need this cfw or wait for rebug to update theirs to use the new dongle update that's coming. I hope they are working on improvement of true blue and not just combating the jb king. Makes me concerned of possible bricking all the tinkering with security features on FW. Whether it's Sony tryin to lockdown my ps3 or true blue, either one of them are capable of doing it if not careful.

to anyone thats updated, id feel peace of mind, hearing your positive results before I try...also are their anything i should know about these patches for downgraded consoles? what does it mean for a non-downgraded console? not trying to be paranoid but we all know the possibilities (ex: waninkokos cfw)

[nativesith]

I updated last night, since it is stated that this v2 CFW is for a upcoming dongle update, and never really noticed any difference. I have not tried any of the 3.56 games yet. Playing Captain America now.=)

[Jay-Jay]

I have not yet updated. I am just being cautious. I have trouble understanding why this information isn't provided in the True Blue official website? Why was it leaked in the underground circuit? I know it could be that they probably don't have someone on staff to do the HTML coding on their site, but still something as important and critical as this, should be released properly, don't you think?

It makes me recall an issue a while back many years ago, when another type of hardware (FTA) were having a clone war. The rival leaked a firmware that bricked many official consoles--which then the official company later released a fix plus then launched their own clone killer. I hope this isn't the case.

[nativesith]

Been on V 2 since last night with no problems.
I hope TB is going to release some new fixes soon=). Why else would we have a V2 CFW and upcoming dongle update? To prevent the fake TB wanna-bes ability to release the new TB game fixes.
Also still having an issue with 3.56 game MK9 which is no big deal since I am playing twenty + TB games=).

[bitsbubba]

Been on V 2 since last night with no problems.
I hope TB is going to release some new fixes soon=). Why else would we have a V2 CFW and upcoming dongle update? To prevent the fake TB wanna-bes ability to release the new TB game fixes.
Also still having an issue with 3.56 game MK9 which is no big deal since I am playing twenty + TB games=).

I've never had any problems with MK9 & TB, hmm?

[nativesith]

Yeah, I tried everything. Deleted all game data, did Updates(101 to 103)tried eboot fix, reripped the game. Still freezes on the MK9 Logo.
I have two ps3's though. One for all True Blue the other is on Rebug 3.55.2 so I can still play the game. Although I do want to use a Cobra USB on that BC Ps3.

[PatrickBatman]

I think it should be stated that one must update from the recovery menu though. I have been having a few issues with 3.56 games, wonder if this update will help. Will those of us on the Rebug TB ed have issues?

I updated fine through XMB. I noticed every 3.56/previously 3.60+ to 3.55 CFW update patch game ive tried to play black screens or freezes (MK9, La Noire, etc) All I've had to do was reinstall the 3.55 fix/update. Of course for LA Noire I had to move it to internal. Rebug on TB will prolly always have issues as it's not OFFICIALLY supported, the TB team doesn't make CFW with rebug in mind i dont think.

Wow a useless update. That does nothing to improve it.

Useless until new updates and games come out, useless now for people not on a downgraded console.

to anyone thats updated, id feel peace of mind, hearing your positive results before I try...also are their anything i should know about these patches for downgraded consoles? what does it mean for a non-downgraded console? not trying to be paranoid but we all know the possibilities (ex: waninkokos cfw)

It means nothing, it wont do anything if you don't have a downgraded console, will just let you install the newest updates and use the newest paradox eboots when they come out.

I updated last night, since it is stated that this v2 CFW is for a upcoming dongle update, and never really noticed any difference. I have not tried any of the 3.56 games yet. Playing Captain America now.=)

If your console isnt downgraded it's GOOD that you have noticed a difference it should function exactly like v1 CFW until new updates and paradox eboots comeon, then the difference will be v1 CFW wont install updates or let you play newest games with paradox eboots and v2 will

I have trouble understanding why this information isn't provided in the True Blue official website? Why was it leaked in the underground circuit? I know it could be that they probably don't have someone on staff to do the HTML coding on their site, but still something as important and critical as this, should be released properly, don't you think?

It makes me recall an issue a while back many years ago, when another type of hardware (FTA) were having a clone war. The rival leaked a firmware that bricked many official consoles--which then the official company later released a fix plus then launched their own clone killer. I hope this isn't the case.

The true blue website wasnt put up for support it was just put up in a hurry for all the people complaining out there not being an official website, if you go there it specifically tells you scene sites to go to, to get support.

As for "the rival leaked a firmware that bricked many official consoles..."
Hence why a MD5 checksum is provided: MD5: ff689e1e8cdd02a46ddadb14c3c5b85c I guess you don't know what this is for (yes the "rival" could release a fake MD5 checksum but as soon as a few people install they'll realize it and if are courteous and smart will reveal this checksum online so no one installs a .PUP with that checksum)

Basically just download the v2 CFW from anywhere (if you want to test) get a checksum calculator and compare the checksum I provided with the one that's calculated from the downloaded PUP if they match its safe if they dont it isnt safe to install.