[NEWS] Cobra 7.0 (unofficial) implementato in rogero 4.46 v1.0

[Tommino81]

Non molto tempo fa' , nella news del rilascio dei sorgenti della dongle usb (TEAM COBRA) fu' accennato, come con tali sorgenti ,potessero essere implementati delle funzioni nei nuovi cfw .

alcuni sviluppatori come Deank e Utente hanno fatto uso di questi sorgenti , ma con molte funzioni di sicurezza integrate , cosi' il capo swiluppatore del TEAM COBRA, ha rilasciato dei nuovi sorgenti

con molte informazioni in piu' , e con la rimozione delle caratteristiche di sicurezza della chiave hardward.

Lo stesso sviluppatore ha poi implementato COBRA nel cfw ROGERO 4.46 v1.0




lo sviluppatore ci tiene a precisare , che tutto è opera sua in veste non ufficiale , e che ilresto TEAM COBRA non ha partecipato al progetto COBRA 7.0


COSA è COBRA 7.0?

* non è un cfw come molti potrebbe pensare

* è un''insieme di 7 file

lv2_kernel.self, ps2_emu.self, ps2_gxemu.self, ps2_netemu.self, stage2.bin, ps2hwemu_stage2.bin e ps2gxemu_stage2.bin

i primi 4 file , sono un mix di CEX 4.46 e OFW e file del cobra

gli altri sono nuovi e non sono presenti in OFW

COME ISTALLARE COBRA 7.0

istallare un CFW CEX 4.46 , insieme ai 7 file del pacchetto

istallare mmCM 4.18.pkg

(attenzione questo non cancella la versione di multiman che avete istallato , ma aggiungera' mmCM ad essa)

dopo l'istallazione di questo pacchetto , multima potra' funzionare in due modalita'.

Multiman e mmCM

PER ISTALLARE I 7 FILE SU UN CFW 4.46 CEX

• CORE_OS_PACKAGE: lv2_kernel.self (sostituire)
  
• / Dev_flash/ps2emu/ps2_emu.self (sostituire)
• / Dev_flash/ps2emu/ps2_gxemu.self (sostituire)
• / Dev_flash/ps2emu/ps2_netemu.self (sostituire)
• / Dev_flash/sys/stage2.bin (aggiungere)
• / Dev_flash/ps2emu/ps2hwemu_stage2.bin (aggiungere)
• / Dev_flash/ps2emu/ps2gxemu_stage2.bin (aggiungere)

LV1 patch necessarie per COBRA 7.00:

* Protezione lv2_kernel rimosso. Gravità: OBBLIGATORIO.
*Lv1 peek / Poke. Necessario per la patch per i dischi ottici PS2 e per lv1_peek/poke in LV2. Gravità: OPTIONAL, senza questo, sarà interessato solo quelle caratteristiche.

Per la compatibilita' con altri cfw 4.46 , varie problematiche (essendo versione unofficial) vi invito a leggere il redame , e/o maggiori informazioni sul thread di riferimento citato nella fonte,
il forum non si assume nessuna responsabilita' su danni arrecati alle vostre consol, è consigliabile fare (sempre prima un dump della NAND/NOR)

Changelog

Changes from Cobra USB 6.0->COBRA 7.0:

Cobra USB device related functions removed. Syscall sys_cobra_usb_command is still there for compatibility reasons, but it will do nothing.

Code cleared from encrypted functions, data and other security measures like the randomization of data or code not longer needed.
Stage 1.5 removed from both, lv2 and ps2emu. There is still a stage 1.5 lan -compiles as stage2.bin-, but that is for developers only.
Stage 1 security garbage removed, now the code can be easily understood
Support for cobra encrypted sprx/self is still kept for compatibility reasons, but security that would protect them from easy methods of dumping has been removed.
drm.c file is still kept for compatibility with already existing compiled versions of netiso.sprx used by mmcm.

(Dirty patch improved)
Text section of vsh.self was made writable by a patch.
This indeed made the memory writable by direct access, but functions like copy_to_user or copy_to_process would still think the section was read only.
The patch has been replaced with a better one that fixes this issue.

PSP mode selection will not longer take effect. Although it was not told to user at that moment, mode 2 made Cobra to use the psp emulator taken from 4.00 OFW (decrypted long ago before keys were released, with a lv2 kernel exploit I discovered) and hidden in the last version of psp launcher.
This made sense for 3.55, since the compatibility of both emu was different (including some regressions in 4.00), but it doesn't makes sense to use 4.00 emulator now.
Maybe it would be a better idea to package the 3.55 one, but not done.
Technical details: cobra syscall sys_psp_set_emu_path will return success, but it will do nothing.

Support for PS2 isos in non BC consoles was removed in 4.30, due to ps2_softemu missing. It has been reenabled now by hacking of ps2_netemu.
You can use it in the same way as before, just load an iso and launch from disc icon, Cobra core takes care of rest.
No need for encrypted isos, isos patched with limg sectors, etc. Just your normal PS2 isos dumped from discs or taken from somewhere.
However, there is no support for optical discs in ps2_netemu. Don't forget to set the memory cards in XMB, in the old memmory card utility for PS/PS2, as ps2_netemu won't let you assign them in game.
BC consoles will still use their respetive emulators (ps2_emu, ps2_gxemu), which have much better compatibilty and also support optical discs, original or backup.

Support for setting fake version was removed in 4.30, since it was permenanetly faked as 4.31. It has been readded, but it will need update on mmcm to use that again.

Cobra USB read its configuration from spi flash. COBRA 7.00 reads it from "/dev_hdd0/vm/cobra_cfg.bin".
When no setting has ever been written, the file will not exist and configuration will have default values. Due to the different timing in which Cobra USB and COBRA 7.00 read the configuration, some others changes in code were needed.

Added partial emulation of READ TRACK INFORMATION command and updated the READ TOC/PMA/ATIP and READ CD commands partial emulation (LV2 only).
This fixes a bug when playing CDDA tracks of psx/ps2 bin/cue images in the XMB player. This didn't happen in 3.55, but Sony changed the code of the audio player at some point after that.

The patches to force XMB load psp launcher, which is a total invalid psp mini package, had some side effects on DRM content, such as ps2 classics.
Now the patches are only done after loading a psp iso, and they will be undone once the manager unloads the psp iso.
Note to users: Don't run any DRM content while there is a psp iso loaded (psp launcher icon not black), it may not work and it may cause the XMB to delete the rif data!

Added support for plugins at boot time. The number of vsh plugins has been increased from 1 to 7. Slot 0 is reserved for use for iso plugins (netiso.sprx and rawseciso.sprx).
Slots 1-6 are for boot plugins.
Plugins are loaded in the following way: text file /dev_hdd0/boot_plugins.txt shall contain a plugin path per line.
Some currently developed plugins like the test one from prxloader don't work (they actually load, but don't work), because they expect that network is already prepared, which is not the case at boot time.
Note for plugin developers: when making a boot plugin for Cobra, if your plugin requires something that is not up yet (like network), just do some waiting at main thread (NEVER in module start, or you'll delay the whole system!), 3 seconds should be enough.
Or just check that network is ready, which is the proper way.

Because of the posibility of a boot plugin crashing the system and causing a pseudo-brick exists, a safety system has been designed:
Enter ps3 recovery mode and select the option "Rebuild database". The recovery process, emer_init.self, will mount dev_hdd0 for a short moment, Cobra core will detect that and it will delete boot_plugins.txt.
Cobra core won't load vsh plugins when there is not VSH: like for example, in recovery and update modes.

Note to developers: please design plugins in such a way that they can be unloaded and they free all resources when that happens.
A sample boot plugin called "testplugin.sprx" is included here. It is a simple plugin that will poweroff the ps3 when L3+R2+X is pressed, or reboot it if L3+R2+O.
Plugin uses an internal vsh function, which does a clean powerroff/reboot, unlike directly calling sys_sm_shutdown.
If you are in a game, enter PS menu to make the combination work.

Added peek, poke, lv1_peek (partial, continue reading), lv1_poke and lv1 call syscalls.
Cobra core wasn't originally developed to coexist with other payloads. As soon as I enabled all these syscalls, a lot of incompatibility problems and payloads and applications destroying some patches that Cobra needs, happened.
So I decided to add a compatibility layer. This is, a custom implementation of all of these syscalls, where Cobra core detects the most common problems.
For example, Iris Manager would temporally load its syscall8, removing the Cobra one. Cobra core is now aware of this, and instead of letting Iris Manager change the syscall address, it concatenates both syscalls: cobra syscall 8 will call Iris syscall 8 when the opcode is not for Cobra.
That was just one of the incompatibilities. Some other incompatibilities have been resolved for the following 3 programs: Iris Manager, Multiman (in multiman mode, see below), and vsh prx loader.
The relevant parts of the compatibility layer are in stage2/main.c
I didn't test all features of those programs, therefore, it is possible that something in them causes problem to Cobra core or that Cobra core causes problems to them.
If you see something odd happening, just reboot the ps3.

After installation of mmCM over Multiman, Multiman will have two modes: "Multiman" and "mmCM".
The first one for regular cfw, the second one for cobra cfw. Multiman detects which cfw is in, and loads the proper self.
Now the problem: when I enabled those syscalls, multiman thought it was in a regular cfw and wouldn't launch mmcm.
So I made a workaround: if multiman is launched from its original location, /dev_hdd0/game/BLES80608/USRDIR/EBOOT.BIN, cobra will block lv2_peek access for the process, to force multiman detect Cobra.
Now, because I also wanted to have a way of launching multiman in its normal mode, there are two ways:
1) Install multiman in a different location (untested). Then, BLES80608 would be mmCM, and the other would be multiman.
2) If L2+cross is kept pressed while launching multiman from BLES80608, Cobra won't block access to lv2_peek, and multiman will load in "multiman mode".
The relevant parts of the code for this are in stage2/modulespatch.c

lv1_peek syscall VS Cobra syscall 8.
Because lv1_peek syscall in lv2 is also syscall 8, the support of Cobra for lv1_peek is partial.
If the address queried is >= 0xA000, Cobra core will do a normal lv1_peek. If its below 0xA000, it will run the specific cobra sub syscall.
Now, this would still cause problems, as some programs -lv1 dumpers- would soon or later crash the system while dumping 0-0xA000, by accidentally calling a Cobra subsyscall.
Cobra core is now aware of this and will temporally block a process from using syscall 8 if it detects it is a possible lv1 dumper, only until some condition is met (like reading from >= 0xA000).

For developers, a proper way to guess if you are in a Cobra cfw is this (if my memory doesn't fail me, this piece of code would work even in Cobra USB 1.0!)

Code:
static inline int sys_get_version(uint32_t *version)
{
system_call_2(8, SYSCALL8_OPCODE_GET_VERSION, (uint64_t)(uint32_t)version);
return (int)p1;
}

int am_i_in_cobra(void)
{
uint32_t version = 0x99999999;

if (sys_get_version(&version) < 0)
return 0;

if (version != 0x99999999) // If value changed, it is cobra
return 1;

return 0;
}

(Other code changes)

SELF/SPRX patch offsets are now in modulespatch.h instead of modulespatch.c. Also, the self/sprx offsets in storage_ext.c (video mode patch) and psp.c has been moved as well to that file.
There shouldn't be any self/sprx offset/address left that is not in modulespatch.h.
config.ps2softemu set value ignored now. Cobra will always do those patches in non BC consoles.
Added cobra syscall sys_sm_ext_send_poweroff_event, which allows Cobra to send a poweroff/reboot event to VSH (cleaner poweroff than sys_sm_shutdown).
Usage is simple: syscall8(SYSCALL8_OPCODE_SEND_POWEROFF_EVENT, reboot_boolean);
Now pad can be read from kernel mode (lv2/pad.h)
"laboratory.c/h": File unused in compiled version of stage2. It is there just in case someone wants to do tests...

fonte

[alexpierotti]

grazie tommy, come sempre sei prezioso come l'acqua(vite)

[Tommino81]

Grazie Alex , anche tu sei prezioso come l'acquaraggia


Inviato dal mio ZP980

[amon76]

Enrico oggi non mi hai cacato proprio! ;(
Bella news by the way?..

[spyro82]

ormai non caga piu nessuno e diventato imprenditore

[amon76]

Ahahahahh...manuele...almeno io è te ci sentiamo dai....mi consolo....

[Tommino81]

ormai non caga piu nessuno e diventato imprenditore

l'imprenditoria la lascio a te' (troppo complicato per me') io mi limito all 'hobbistica e portare avanti quei due/tre impegni che ho preso.
mimmo quando vuoi.....

[pigma]

Ciao tutti e grazie sempre dell'ottimo lavoro

Scusate ma ho un dubbio ma c'è qualche ODE o qualche homebrew o quello che sia che funzioni su ofw superiore a 3.55 PS3 ?

[Razorbacktrack]

???

Inviato dal mio B6000 utilizzando Tapatalk

[Tommino81]

sezione non è appropriata direi....

per ide (volevi mica dire ode?)

[pigma]

sezione non è appropriata direi....

per ide (volevi mica dire ode?)

Ops !

Si "ODE" XD

NOn era mia intenzione rovinare questo bel post

Avevo questa domanda da porvi mi aiutate ??

[Tommino81]

Tranquillo non era un rimprovero.
Questo e un cfw con implementati i sorgenti del cobra rilasciati tempo fa'....

Inviato dal mio ZP980

[pigma]

Tranquillo non era un rimprovero.
Questo e un cfw con implementati i sorgenti del cobra rilasciati tempo fa'....

Inviato dal mio ZP980

Mi aiuti a capire se c'è un ODE che funzioni con ofw superiore a 3.55 for ps3 ?

[Razorbacktrack]

Gli ode funzionano con qualsiasi OFW,per me però non sai nemmeno di che stai parlando..

[Tommino81]

Mi aiuti a capire se c'è un ODE che funzioni con ofw superiore a 3.55 for ps3 ?

premesso che non sia la sezione adatta .
se devi montare un odde su ps3 (non downgradabili) vai tranquillo che puoi modificarla appunto con (odde)
basta vedere quale sia compatibile con la tua ps3 !

[pigma]

premesso che non sia la sezione adatta .
Se devi montare un odde su ps3 (non downgradabili) vai tranquillo che puoi modificarla appunto con (odde)
basta vedere quale sia compatibile con la tua ps3 !

grazie mille

[pigma]

[QUOTE=Razorbacktrack;198703]Gli ode funzionano con qualsiasi OFW,per me però non sai nemmeno di che stai parlando..[/QUOT]

Se sai tutto tu mi fa piacere sono contento per te ciao

[Razorbacktrack]

Non è che so tutto io, io mi documento, cerco e non do risposte inutili come quest ultima tua. Se non sai le cose, prima di unire parole a cazzo, ti basta leggere un tutorial. Oltre a questo, la tua domanda non c'entra una sega con la news quindi chiudiamo questo OT, grazie

Inviato dal mio B6000 utilizzando Tapatalk

[pigma]

Non è che so tutto io, io mi documento, cerco e non do risposte inutili come quest ultima tua. Se non sai le cose, prima di unire parole a cazzo, ti basta leggere un tutorial. Oltre a questo, la tua domanda non c'entra una sega con la news quindi chiudiamo questo OT, grazie

Inviato dal mio B6000 utilizzando Tapatalk

Sei uno stronzo questo c'èntra col tuo linguaggio pensavo che ci fossero delle regole in questo forum come vedo non valgono per tutti

[Razorbacktrack]

Io sono uno stronzo,ma tu sei bannato

P.S. Le regole ci sono solo quando fa comodo,vero?