[H3avyRa1n]

people started to make judgments without testing the thing (which is normal considering the amount of trash that is released) but you can't take it as a personal attack.

Thanks @Descrambler

[Warning]

Still interested to see how this was done. The eboot does seem to be 3.70 and unmodified.

[VIRGIN KLM]

Originally Posted by erexx Every "eboot.bin" and "iso.edat.bin" is Unique to that specific game. Just like you were confused and flat wrong about Minis games... remember that?

Ah please stop, enough already OK?
I'm not cunfused and flat for nothing, it's obvious to everybody that you are obsessed with me so accept it.
If I was wrong the PSP emulator patch I did wouldn't work flawlessly on Cobra CFW even though on 3.55 it stays idle and it's normal plus if I was wrong about the ELFs used on EBOOTs of games that mainly use the same game engine or exactly the same with different file lists the recent semipatches of EA Sports games wouldn't work.
Next time you use your arrogacy, be aware that somebody could do it better than you.

[H3avyRa1n]

Originally Posted by Warning Still interested to see how this was done. The eboot does seem to be 3.70 and unmodified.

so that makes it 2 of us.. this really is intrigant

[nu9000]

Thanks Descrambler works great on 3.41.

[Descrambler]

Updated post #1 - have phun !

[Warning]

Thanks for the explanation.
I hope we can see more tricks ;-) in the future

[Mistawes]

Interesting find, good work!

[lukethomasx]

Originally Posted by Descrambler Here's my fix for Singstar - Back to the 80's -BCES01257 Original requires FW 3.70 Howto: 1. Download THIS SingStar Update and copy it to the root of your USB Stick 2. Install the Singstar Update PKG via "Install Package Files" 3. Copy my attached PARAM.SFO into your Singstar 80's folder and replace the original one. Normally /BCES01257/PS3_GAME/PARAM.SFO 4. Mount 80's Disc with Multiman and run it. That's all. What i forgot: When u start the game the 1st time and you're console is connected to the internet - Singstar will ask to install Update 5.12 - Do NOT install 5.12 on ANY Singstar Version - Then Singstar requires 3.70 again ! ------------------------------------------------------------ So here's the explanation of the trick: When the system launches a disc, it gets the Title ID - in our case BCES01257 - from the PARAM.SFO of the disc. There are no checks if the eboot will fit for that PARAM.SFO - So it can mismatch without having any issues. But what the system checks is if there are updates installed for the Title ID : root/game/BCES01257/ So i patched the PARAM.SFO to Title ID BCES00494 - That's Singstar Queen. And the linked update BCES00494.pkg contains a 3.41 EBOOT.BIN that includes a full Singstar 5.10 player software for the new generation of Singstar discs (With PSMove support and Singstar Guitar). So the 80's disc launches and sees the updated player in root/game/BCES00494/ and lauches this instead of the 3.70's EBOOT on the disc. Theres also the possibility to depkg the queen update and change all BCES00494 Id's to BCES01257 and create a fake 80's update. I decided to patch as less as possible to keep the files original and used this nice trick ;-) Thanks for listening.

So could the same thing potentially work with a game like lego pirates?

[kejdikola]

Something is confusing here:
In the picture that member have attached it show playing the game while pressed the PS button
Now this part is very weird. If you see the picture carefully you will se it has the Tv Section and also the Install Package and app/home etc.
So we can call this a fake or a 3.70+ CFW
Any thought ?