Rogero Manager v8.5 Solar Edition

[Rogero]

Is it just me, or ist Rogero Manager moving the Folder "PS3_Game" into the Root of my External HDD.

Last Night i was playing Fight Night Champion...this morning i was downloading some Stuff and saw that the "PS3_Game" Folder of FNC is in the Root. Same with Crysis 2, each Time i play a Game with Rogero Manager, i need to move the PS3_Game Folders back to the Original Folder.

Can anyone confirm this?!

Yes, the manager will move the PS3_GAME folder to root of your USB device when you load a game with [USB_MOUNT] = On , this is how [USB_MOUNT] works, and when you start the manager next time, it will restore the folder automatically to the respective game's directory, so you don't have to worry about it.

N.B: both multiMAN and Rogero Manager use the same technique for USB game mounting (this great method was implemented by Deank) , and they are compatible one with the other, example:
you can USB_MOUNT a game with multiMAN then start Rogero Manager and it will restore the folder to the game's path without any problem and the other way around.

[Rogero]

rogero is there any way you can improve discless support????

I don't think so, some games have additional checks that can't be bypassed.

[Rogero]

Last night I added support for auto-loading the PL3 payload for MFW 3.15 / 3.41, so now the manager will detect the MFW version and will load the appropriate PL3 version for it, no more dongles needed for MFW 3.15 / 3.41 and off course for MFW 3.55 there is still Syscall36 or PL3 available.

Credits goes to An0nym0us for his newly released payload loader called "Payloader3" that made this possible

This is a link to the Beta version of Rogero Manager 8.3 in case you wanted to try the MFW3.15/PL3 auto-loading.
Rogero_Manager_v8.3_Beta_Test_PL3_Support_for_MFW_ 3.15_3.41

I still have to finish some functions in version 8.3 before the final release.

N.B: MFW3.15/3.41 must not use any spoof for the manager to detect the correct version and load the
appropriate payload, with spoofing it will fail.

Cheers

[CallMeTheDevil]

Ah, okay, thanks for the Information.

I didnt know how exactly the USB-Mount Stuff works!^^

[Rogero]

I just wanted to tell you about the new IRC channel #Rogero_Manager on Efnet Servers, where me and some other friends can answer most of the questions regarding the manager while we're online on IRC.

The reason for creating this channel is: that Lately I was spending much time online and on IRC (mostly in the famous #multiMAN with deank and other great friends there) and sometimes I had to answer questions about Rogero Manager in #multiMAN, which I thought was not appropriate, that's why I created the new channel.

Cheers.

[ieder-zijn-meis]

MFW 3.15 spoofed to 3.60 (3.60 48686 001:CEX-ww) *
- just blackscreens on v8.3 Beta on both [Dean 36] and [PL3] - version is detected as 3.60

MFW 3.15 spoofed to 3.60 (3.60 48686 001:CEX-ww) * [PL3 patched] **:
- v7.5/v7.6 runs/detects just fine PL3, version is detected as 3.60
- v8.3 Beta runs/detects just fine PL3, version is detected as 3.60

so my guess is that it is failing to detect the spoof and handles it as 3.55++

*) MFW 3.15:
- Patched LV1 hypervisor to allow mapping of any needed memory area
- Patched LV2 kernel to add Peek&Poke system calls to LV2
- Patched PKG installer to allow installation of pseudo-retail + debug PKGs
- Patched Application launcher to allow running of unsigned applications
- Added Install PKGs + /app_home
- Spoof firmware build/version to 3.60 48686 001:CEX-ww

**) PL3 patched:
- External injected PL3_DEF_315 to LV2


Fixed version: ps3mfw-w32_portable.rar (4.4 MB) http://www.multiupload.com/QSFVE64T72

[Rogero]

MFW 3.15 spoofed to 3.60 (3.60 48686 001:CEX-ww) *
- just blackscreens on v8.3 Beta on both [Dean 36] and [PL3] - version is detected as 3.60

MFW 3.15 spoofed to 3.60 (3.60 48686 001:CEX-ww) * [PL3 patched] **:
- v7.5/v7.6 runs/detects just fine PL3, version is detected as 3.60
- v8.3 Beta runs/detects just fine PL3, version is detected as 3.60

so my guess is that it is failing to detect the spoof and handles it as 3.55++

*) MFW 3.15:
- Patched LV1 hypervisor to allow mapping of any needed memory area
- Patched LV2 kernel to add Peek&Poke system calls to LV2
- Patched PKG installer to allow installation of pseudo-retail + debug PKGs
- Patched Application launcher to allow running of unsigned applications
- Added Install PKGs + /app_home
- Spoof firmware build/version to 3.60 48686 001:CEX-ww

**) PL3 patched:
- External injected PL3_DEF_315 to LV2

Hello,
thanks for the feedback, I forgot to mention that MFW3.15/3.41 must not have the version string spoofed for the manager to load the appropriate payload, because it considers everything > 3.55 as a spoofed CFW3.55 and in that case it will load Sysc36/PL3 for FW3.55, that's why it fails on 3.15/3.41 while poking the payload into memory and you see a Black screen.

For Now, just use MFW3.15/3.41 without spoofing and the manager will work fine.

Cheers

[ieder-zijn-meis]

Hello,
thanks for the feedback, I forgot to mention that MFW3.15/3.41 must not have the version string spoofed for the manager to load the appropriate payload, because it considers everything > 3.55 as a spoofed CFW3.55 and in that case it will load Sysc36/PL3 for FW3.55, that's why it fails on 3.15/3.41 while poking the payload into memory and you see a Black screen.

For Now, just use MFW3.15/3.41 without spoofing and the manager will work fine.

Cheers

Yeah, figured it worked that way

Quick fix would be to add an option in settings: [Dean36] [PL3] [no payload] and use [no payload] as default or after error

BTW if you unself vsh.self of 'MFW 3.15 spoofed 3.60' you can check that it is using a rev 0x01 key and not rev 0x0D or later (so it must be a spoofed 0.92-3.31). Shorted check to look for is the curvetype, but if you want to be really sure I recommend longer values like erk/riv/pub (e.g. isoldr 3.50 uses same curvetype as lv2ldr 3.56 and future TBA FW version may repeat the appldr curvetype of previous versions)

0.80-0.92 (rev 0x00) - curve_type: 0x21
0.92-3.31 (rev 0x01) - curve_type: 0x11
3.40-3.42 (rev 0x04) - curve_type: 0x14
3.50 (rev 0x07) - curve_type: 0x15
3.55 (rev 0x0A) - curve_type: 0x25
3.56 (rev 0x0D)- curve_type: 0x12

I'm not sure if you can succesfully identify the exact version of a spoofed model (in my example I am only able to detected a spoofed 3.60 to be a 0.92-3.31, but not pinpoint it exactly to 3.15 wich is needed to use the correct offsets for the payload). But this could give the option to detect spoof and disable the payload complety, or give the user a messagebox "spoofed version detected, please set the REAL fw version"


Fixed version: ps3mfw-w32_portable.rar (4.4 MB) http://www.multiupload.com/QSFVE64T72

[Rogero]

Yeah, figured it worked that way
Quick fix would be to add an option in settings: [Dean36] [PL3] [no payload] and use [no payload] as default or after error

Hi again, actually this won't work, because the manager checks for any payload type present at startup (Hermes/PL3/Dean's Sysc36/PSgroove1.1/PsGroove1.0) and only when no payload detected, it will check the PS3 version and try to load the correct PL3 file for that version (3.15/3.41/3.55), and only for 3.55 it will give you the option to choose between Sysc36 and PL3.
So you can still use any USB dongle/payload and it will detect it and works fine too.

0.80-0.92 (rev 0x00) - curve_type: 0x21
0.92-3.31 (rev 0x01) - curve_type: 0x11
3.40-3.42 (rev 0x04) - curve_type: 0x14
3.50 (rev 0x07) - curve_type: 0x15
3.55 (rev 0x0A) - curve_type: 0x25
3.56 (rev 0x0D)- curve_type: 0x12

I'm not sure if you can succesfully identify the exact version of a spoofed model (in my example I am only able to detected a spoofed 3.60 to be a 0.92-3.31, but not pinpoint it exactly to 3.15 wich is needed to use the correct offsets for the payload). But this could give the option to detect spoof and disable the payload complety, or give the user a messagebox "spoofed version detected, please set the REAL fw version"

Thanks again for this additional info, this is what i wanted to check about and do some testings in order to have a solid and reliable PS3 version detection.
And if nothing of this worked as expected, then a Dialog Screen will be used to tell the user about the spoofed Version which will prevent the manager from crashing

Cheers.

[ieder-zijn-meis]

great Rogero

pasting it here for convenience....

another method to detect a spoof might be dev_flash/vsh/etc/version.txt and grep the builddate:

315=	20091206:tetsu@tetsu-linux18.rd.scei.sony.co.jp
341=20100721:tetsu@tetsu-linux22.rd.scei.sony.co.jp
350=20100913:tetsu@tetsu-linux14
355=20101127:tetsu@tetsu-linux14
356=20110129:tetsu@tetsu-linux16
360=20110304:tetsu@tetsu-linux15

so a spoofed 3.15 will have a version string in SystemInfo of 3.60 but a builddate of 20091206 besides the above posted used vsh.self keys "0.92-3.31 (rev 0x01) - curve_type: 0x11"


Fixed version: ps3mfw-w32_portable.rar (4.4 MB) http://www.multiupload.com/QSFVE64T72