the-green

t'utilise quoi comme émulateur ? tu dois mettre le dossier de l'émulateur à l'intérieur duquel se trouve un fichier eboot.bin, dans le dossier PSP/GAME/ de votre carte mémoire une fois l'émulateur détecté et se lance tu n'as qu'à mettre tes backups dans le dossier ROM qui se trouve dedans bonne chance

un mm avec qq options sur seulement la gestion des images iso PSX/PS2/PSP sans pouvoir les lancer qq jaquettes PSX/PS2/PSP et PS3 en plus et qq options sur la copie des fichiers de + de 4GO sinon, ça marche comme le simple multiman sur mon CFW rebug 3.55.2

Bonjour les gars bah c'ets une puce glitch tout en un, voilà...un peu mieux que squirit 360 qui lui nécessite le programmateur externe, là tout est dedans voici les options disponibles dessus * JTAG programming of onboard Xilinx via USB (No external programmer needed) • SPI Progamming of Xbox360 NAND via USB (No external programmer needed) • Fast swap between SPI and JTAG modes with a press of a button • Firmware upgradable for future XAIO 360 updates (No external programmer needed) • External Oscillator (Wiring to HANA is no longer required) • 100% Compatible with NAND Pro v2.0 (3.0 is NOT supported!) • Compatible with all Xbox360 models (Except Xenon and Corona boards) • Booting of unsigned code on Xbox360 • Compatible with all Xbox360 kernel versions • Very stable glitch times for both PHAT and SLIM (Usually within 3-30sec) • Easy 7 wire SPI installation for both PHAT and SLIM • Easy 5 wire RGH installation for PHAT, 6 wires for SLIM • Full 11 wire SPI/RGH installation for PHAT, 12 wires for SLIM (Only 1 GND point is needed so 1 less wire!) • Works as 6 wire JTAG-interface using UrJTAG* software (4 signals + power (TDI, TMS, TCK, TDO, VCC, GND)) *** Required patched version of UrJTAG will be downloadable from our website. • Compact size of 47mm x 32mm (1.84" x 1.28") Source: http://www.ps3crunch.net/

Joli coup de la team cobra, enfin une méthode pour convaincre les gens d'acheter ce dongle qui mérite grandement le respect. Bonne continuation team cobra Voici le changlog total Changelog (for users updating from multiMAN 02.09.02 to multiMAN/mmCM 04.00.00): ================================================================================ * Added function "Create ISO from folder" * Support for *.0/.31, *.001/.032, *.66600/.66631 split file formats * Join split files in file manager (select and copy the first file to get the rest joined) * New display mode "XBDM" - XBOX Dash Clone * Added option "Detect Game Title in ISO Images" to allow using ISO filenames and *not* scan for game names in local database * Improved scanning for retro roms/iso and covers (populating the Retro column) * New THEME format (.thm). One theme - one file. Easy installation within multiMAN/mmCM without going to XMB to install theme pkg files. * mmTM - Easy to use PC application to create thm files from folders (separate download). * multiMAN/mmCM will try to read disc volume labels and display in VIDEO column (BD/DVD entry) and in other display modes. * Added indication (rotating refresh icon next to the column icon) when multiMAN/mmCM is loading/extracting title thumbnails (XMMB mode) * Added pop-up notifications when new versions of multiMAN/mmCM and Showtime are available for download * Added pop-up notification when running low on disc space (less than 1GB on internal HDD) * Added pop-up notification when multiMAN/mmCM successfully connects to nethost folders during startup (/net_host# in File Manager) * Added support for downloading themes in a background thread (pop-up messages will notify user when download starts and completes) * Added support for copying big (4+GB) files in File Manager to USB drives. multiMAN/mmCM will split source file when copying to USB. * Changed option "Link Video Library to Showtime" - it will only create links for XMB Video files, but will not start Showtime * Added shortcut (virtual folder) "XMB Video Files" when browsing HDD/USB drives in VIDEO column * Added "Showtime Font Preference" option to select 10 different fonts for SHOWTIME media player (GUI and Subtitles) * Added support to extract PSP CSO (compressed ISO) files in XMMB/XBDM display modes and File Manager (extracted image is saved in /dev_hdd0/PSPISO) * Added shortcut to ISO folder when browsing external USB devices (PSP connected with memory stick /ISO folder, containing CSO and ISO files) * Added music playback fade-out when leaving multiMAN/mmCM * Added download progress indication in XMMB/XBDM modes - Web column. An entry will show current download filename and percentage of completion. * Added TextViewer in File Manager (supported files colored in light blue). Supports viewing of ANSI/UTF plain text files. * TextViewer controls: L1/R1 - PageUp/PageDown, L2/R2 - zoom out/in (50%-250%), R3 - change font, UP/DOWN/LEFT/RIGHT - scroll/pan, L1/R1+SELECT - skip to start/end of file * Added support for browsing Video, Games, Favorites and Retro (ROMS/PS1/PS2/PSP) in "Coverflow" display mode. Change content mode with UP/DOWN. * Improved performance when extracting CSO to ISO and when creating ISO files from folders * SIXAXIS gyroscope affects screensaver mode (wave/tilt the controller to navigate the starfield) * Improved "Coverflow" display mode

La méthode kamikaze sert à débloquer la protection write sur les liteons slim Winbond en perçant le chip à un point précis le kamikaze template est une idée développée par la team maximus histoire de faciliter la localisation de ce point

Cobra lance tous les jeux sans bluray sous la forme iso mais ne lance pas les jeux 3.6+ Trueblue lance les jeux 3.6+ mais certains nécessitent le bluray pour se lancer après tout, êtes-vous sur de ton problème ?? t'es en quel firmware ? une PS3 avec carte fille HS ne lance pas les hombrews et l'installation des firmwares échoue dessus.

La team rebug (Evilsperm et cyberskunk) bien connus sur la scène PS3 par leurs CFW Rebug 3.41/3.55, leur spoof versions et leur Toggle QA Flag, préparent leur rentrée sur la scène XBOX 360. La team a mis en ligne un nouveau site web qui accompagnera leur nouvel produit qui sera nommé XAIO 360. Pour le moment, la team rebug n'a donné aucun détail sur leur XAIO 360, toutefois et selon GaryOPA (administrateur de ps3crunch et très rapproché de la team), ça ne sera pas une simple puce RGH mais un truc carrément révolutionnaire, elle concernera tous les possesseurs de la XBOX 360 !! Sur le site officiel de ce produit, on remarque un compte à rebours de 12 jours, donc si vous voulez savoir c'est quoi ce XAIO 360, rendez-vous dans 15 jours à l'adresse suivante. http://www.xaio360.com/ Source: http://www.ps3crunch.net/ Voici le site PS3 de la team rebug: http://rebug.me/ Donc, selon la photo, ça sera quoi selon vous ?

Y a pas de quoi, merci à ps3news personnellement pour cette info Bon, oui le passage parlant du dump décrypté/write et en full software a l'air d'être super intéressant, si ça réalise ça peut nous ouvrir une autre voie pour les backups PS3 en OFW 4.00 donc avec PSN !! lol, je sais que 'est difficile mais bon...sait-on jamais, 2012 nous rapportera certainement qq nouveautés pour la PS3 QQ chose me dit que c4eva va parler de ce sujet sur irc lui aussi....patience .

ça commence :encolere12: restez dans le sujet les gars...les critiques allez-vous ailleurs.

Salut les amis, de nouveau MathieuLH et lors d'une petite discussion sur IRC avec un certain XLoader, il nous livre qq informations sur pas mal de sujet tournant autour du hack PS3, le lecteur BluRay, son dump/write, les firmware 3.56 et les firmwares 3.6+, la rootkey et les npdrm. Dump LV0 3.55 [20:10:59] <Mathieulh> you just need a freaking infectus [20:11:05] <Mathieulh> and coding skills [20:11:21] <Mathieulh> you patch lv1ldr [20:11:26] <Mathieulh> so that when lv0 loads it [20:11:33] <Mathieulh> lol [20:11:42] <Mathieulh> yah I have read 3.55 xD [20:11:49] <Mathieulh> 3.55 lv0 is EASY to dump [20:11:58] <Mathieulh> so anyway lv1ldr is loaded by lv0 [20:12:06] <Mathieulh> and has access to all the xdr memory space [20:12:11] <Mathieulh> at least at the time it gets loaded [20:12:15] <Mathieulh> so you can read and write [20:12:20] <Mathieulh> without messing with lv1 [20:12:25] <Mathieulh> well you get the idea [20:12:38] <Mathieulh> of course you have to sign it [20:12:46] <Mathieulh> but it's not like you don't have the keys [20:13:10] <Mathieulh> and it makes things about 300% easier than using lv1 to do the dump [20:13:23] <Mathieulh> because you don't have to touch the xdr at all Rootkey [19:49:22] <Mathieulh> I figured the algo [19:49:25] <Mathieulh> for metldr/bl [19:49:28] <Mathieulh> the one for the encryption [19:49:34] <Mathieulh> and I even got some of the keys they use [19:49:43] <Mathieulh> I can even "calculate" the per console key now [19:49:46] <Mathieulh> but I lack 2 statics [19:50:00] <Mathieulh> and I know how the header is parsed [19:50:17] <Mathieulh> yah, that's what happens when sony reuse the algo somewhere else [19:50:20] <Mathieulh> along with some of the keys [19:50:31] <Mathieulh> I actually had it reversed before but I failed to notice it was the same [19:51:01] <Mathieulh> I can also decrypt the per console key stored in the metldr/bl header [19:51:05] <Mathieulh> the 12 bytes one [19:51:25] <Mathieulh> well actually it's more than 12 bytes because they only use this as par of the key xD [19:51:28] <Mathieulh> well there are 2 [19:51:34] <Mathieulh> one is used to decypt the second [19:51:41] <Mathieulh> which is stored in the metldr/bl header [19:51:57] <Mathieulh> the encryption uses several steps [19:52:07] <Mathieulh> in the end a 40 bytes key is used to decrypt the remaining data [19:52:13] <Mathieulh> woops [19:52:16] <Mathieulh> 0x40 butes [19:52:19] <Mathieulh> bytes* [19:53:09] <Mathieulh> the problem [19:53:20] <Mathieulh> is that I lack the static used to decrypt the other 12 bytes [19:53:25] <Mathieulh> which is the per revision key [19:53:36] <Mathieulh> also stored in metldr/bl header [19:53:58] <Mathieulh> well actually it's not really 12bytes but you need them to form the key [19:54:17] <Mathieulh> cause it's 12 + 4 bytes [19:55:07] <Mathieulh> anyway I am back to do constructive stuffs [19:55:50] <Mathieulh> oh ! also isoldr actually clears the eid root key [19:55:55] <Mathieulh> from offset 0 [19:56:02] <Mathieulh> before passing execution to isolated modules [19:56:06] <Mathieulh> but I can still calculate it back [19:56:12] <Mathieulh> and thus dump it from an isolated module xD [19:56:44] <Mathieulh> eussNL they don't use the 12 bytes as a final key [19:56:51] <Mathieulh> they use 16 bytes total [19:57:15] <Mathieulh> yes, they use 16 bytes key and 16 bytes iv [19:57:18] <Mathieulh> for first step [19:57:23] <Mathieulh> from which 12 bytes [19:57:30] <Mathieulh> are not static [19:57:41] <Mathieulh> and are encrypted [19:57:56] <Mathieulh> by another key/iv [19:58:23] <Mathieulh> (cbc256) [19:58:40] <Mathieulh> I have those for the second 12 bytes [19:59:07] <Mathieulh> they are per console, but I know how to calculate them (kinda) [19:59:26] <Mathieulh> and they are used to decrypt the 12 bytes per console from the metldr/bl header [20:00:48] <Mathieulh> I just lack the keys [20:00:52] <Mathieulh> to decrypt the first 12 bytes [20:00:58] <Mathieulh> used on a per revision [20:01:12] <Mathieulh> otherwise I have the whole algo + header parse + some of the keys [20:04:19] <Mathieulh> kinda [20:04:48] <Mathieulh> it's rather useless anyway [20:04:56] <Mathieulh> because you lack one of the keypair [20:05:07] <Mathieulh> but it's nice to know how the crypto engine works [20:05:18] <Mathieulh> only part of it is there though [20:05:23] <Mathieulh> the header parsing and other shit isn't there [20:05:48] <Mathieulh> and the main 256cbc key isn't there either [20:05:56] <Mathieulh> (the one I got) NPDRM INFO <Mathieulh> btw you can still get homebrews on 3.56 using npdrm and a new pair key but meh... so instead they blacklisted geohot's keypair and added a bunch of other useless checks geohot stuff doesn't generate some of the npdrm specific values those were not checked in 3.55 but they are checked in 3.56 now there is no whitelist for npdrm so it's actually possible to generate valid npdrm self for 3.56+ that tool I made a screenshot of actually does that it's enforced by lv1 though yeah it's a hash but I won't say more everything you need is in the 3.56 fw same checks you won't get around crafting valid 3.56+ npdrm selfs without a proper makeself tool though Bd Firmware [15:48:58] <Mathieulh> uh oh .... I think I may have found a way to dump the decrypted bd firmware from software.... [15:50:36] <Mathieulh> why the fuck did sony engineers had to put some fancy useless hidden debug test mode on their drive ? xD [15:51:46] <Mathieulh> well it IS locked with some stupid "password" [15:51:54] <Mathieulh> but they leaked the "pass" "somewhere" [15:51:57] <Mathieulh> so meh.... xD [15:52:44] <Mathieulh> lol so he could grab my work and call it his own ? Yeah right... xD [15:52:59] <Mathieulh> Melfice shitloads of undocumented commands I can use [15:53:13] <Mathieulh> looking at figuring out the syntax to dump [15:53:30] <Mathieulh> then I can find the key [15:53:35] <Mathieulh> patch the firmware [15:53:38] <Mathieulh> and flash it to my box [15:53:51] <Mathieulh> and make it recognise all my discs as geniune [15:54:04] <Mathieulh> just for the lulz xD [15:54:36] <Mathieulh> of course I need to flash it from 3.55 [15:54:40] <Mathieulh> at least for now [15:54:51] <Mathieulh> the thing doesn't seem to be signed [15:54:56] <Mathieulh> so.... fail [15:55:03] <Mathieulh> it's just crypto [15:55:05] <Mathieulh> you get the key [15:55:11] <Mathieulh> you can make your own firmware [15:55:21] <Mathieulh> and "update" it from the ps3 [15:55:32] <Mathieulh> nah [15:55:44] <Mathieulh> the "password" is an actual key [15:56:01] <Mathieulh> yah [15:56:07] <Mathieulh> 128 bits [15:56:17] <Mathieulh> I have it [15:56:41] <Mathieulh> the command for the test mode is also somewhat hidden [15:56:50] <Mathieulh> but meh.... xD [15:57:19] <Mathieulh> xell you need the drive in the ps3 [15:57:23] <Mathieulh> to use that crap [15:57:26] <Mathieulh> or so I think [15:57:45] <Mathieulh> not sure if it can be used from pc by converting the port to regular sata [15:57:48] <Mathieulh> and I do not plan on doint it [15:57:51] <Mathieulh> doing it * [15:58:16] <Mathieulh> once you get the test mode unlocked you can do fancy shit [15:58:23] <Mathieulh> like read the drive controller ram [15:58:24] <Mathieulh> raw [15:58:27] <Mathieulh> and write to it [15:58:39] <Mathieulh> so I could patch the firmware on the fly for example SPI PWN [23:30:13] <Mathieulh> well so far it's "I am using a lower firmware I can sign on" [23:30:16] <Mathieulh> so meh... [23:31:44] <Mathieulh> if that can change your mood, I actually know how I do it ! [23:32:33] <Mathieulh> good luck exploiting something you can't load [23:35:45] <Mathieulh> you can pwn the ppu through spi bus easily [23:35:56] <Mathieulh> and run code even on cech3000 [23:36:06] <Mathieulh> requires hw though [23:36:09] <Mathieulh> obviously [23:36:18] <Mathieulh> you can use that to pwn the bl [23:36:23] <Mathieulh> if you dunno how to reload it [23:41:30] <Mathieulh> phiren, you can write to xdr [23:41:32] <Mathieulh> through spi [23:41:35] <Mathieulh> not read though [23:41:39] <Mathieulh> but who needs read right? [23:41:43] <Mathieulh> you can allocate ram too [23:41:53] <Mathieulh> you can do nice things basically [23:42:01] <Mathieulh> all through a 50mhz bus [23:42:16] <Mathieulh> they should have a sticker with "insert modchip here" [23:42:27] <Mathieulh> it's still in cech3000 [23:42:34] <Mathieulh> so you can patch ram on the fly [23:42:40] <Mathieulh> and gain control freaking early [23:42:57] <Mathieulh> btw the meta exploit still works on the new bl for what it's worth [23:43:14] <Mathieulh> so you can in theory get it to decrypt lv0.2 for you althouhg that is quite useless [23:43:21] <Mathieulh> you cannot gain code execution though [23:43:28] <Mathieulh> at least I haven't succeeded in it [23:43:52] <Mathieulh> yeah [23:44:04] <Mathieulh> you can do ram patches though [23:44:07] <Mathieulh> if you know the offsets [23:44:18] <Mathieulh> and kill checks [23:44:25] <Mathieulh> the xdr one? [23:44:26] <Mathieulh> nope [23:45:20] <Mathieulh> there is another nice hack phiren [23:45:27] <Mathieulh> there is a test mode pin [23:45:32] <Mathieulh> on the xdr bus [23:45:43] <Mathieulh> which sets the clock to any value you want [23:45:50] <Mathieulh> so you can slow down the xdr [23:46:00] <Mathieulh> and have something attached to it [23:46:03] <Mathieulh> let's say a fpga [23:46:06] <Mathieulh> well you get the idea [23:46:16] <Mathieulh> hw wise the mobo security fails [23:46:26] <Mathieulh> I just fail wit hw [23:46:29] <Mathieulh> with* [23:46:37] <Mathieulh> so I cannot build it mysekf [23:46:39] <Mathieulh> myself* [23:46:58] <Mathieulh> yeah cause that is cpu related [23:47:10] <Mathieulh> but 1. the ldr binaries have bugs [23:47:23] <Mathieulh> 2. There is a hw design flaw [23:47:28] <Mathieulh> which allows through software [23:47:35] <Mathieulh> using lv2 privs or higher [23:47:44] <Mathieulh> to write data at random addresses [23:47:51] <Mathieulh> anywere in the LS of a given spu [23:47:59] <Mathieulh> including the isolated LS [23:48:18] <Mathieulh> the only variable is that you do not control the LS address you hit [23:48:23] <Mathieulh> no [23:48:30] <Mathieulh> that is something I found by mistake [23:48:35] <Mathieulh> and shouldn't even have found [23:48:46] <Mathieulh> it's a pain to use to exploit anything [23:48:49] <Mathieulh> but it can [23:48:56] <Mathieulh> given patience and the right circumstances [23:49:06] <Mathieulh> you can pwn the new metldr with that for exapmle [23:49:35] <Mathieulh> of course some criterias have to be met as well [23:49:38] <Mathieulh> the isolated process [23:49:43] <Mathieulh> has to use a specific function [23:49:52] <Mathieulh> one that sadly is used a lot by loaders [23:49:56] <Mathieulh> or usual spu binaries [23:50:04] <Mathieulh> the more it's used [23:50:14] <Mathieulh> the more often the bug can be triggered [23:50:39] <Mathieulh> zecoxao, which one? [23:50:48] <Mathieulh> the spi fail can be used on current consoles [23:50:58] <Mathieulh> as in cech3k and whatnot [23:51:02] <Mathieulh> ah ! [23:51:04] <Mathieulh> yeah it can [23:51:12] <Mathieulh> works on 3.74 [23:51:24] <Mathieulh> well 4.00 too Clock Rate [23:45:27] <Mathieulh> there is a test mode pin [23:45:32] <Mathieulh> on the xdr bus [23:45:43] <Mathieulh> which sets the clock to any value you want [23:45:50] <Mathieulh> so you can slow down the xdr [23:46:00] <Mathieulh> and have something attached to it [23:46:03] <Mathieulh> let's say a fpga [23:46:06] <Mathieulh> well you get the idea [22:28:09] <Mathieulh> also the xdr clock speed can be descreased [22:28:33] <Mathieulh> Apocalyps, it allows to load metldr at runtime [22:28:39] <Mathieulh> it gets decrypted by the crypto engin [22:28:42] <Mathieulh> and authenticated [22:28:47] <Mathieulh> and then runs in a secure context [22:28:50] <Mathieulh> in isolation mode [22:29:08] <Mathieulh> Apocalyps, you need to exploit the isolated process [22:29:21] <Mathieulh> zecoxao, that's a way [22:29:23] <Mathieulh> there are others [22:31:01] <Mathieulh> if you want to go the hw route [22:31:10] <Mathieulh> do not try to read the shared LS directly [22:32:28] <Mathieulh> randev the LS is only interconnected to the EIB [22:32:40] <Mathieulh> and the EIB can only be accessed from the ppu [22:33:08] <Mathieulh> Apocalyps, go for it then [22:33:21] <Mathieulh> it's not all internal [22:33:37] <Mathieulh> the shared LS can be accessed from the ppu Fake Sign [14:33:39] <Mathieulh> though I can run code on untouched 3.56 but that's just me [14:33:51] <Mathieulh> I have to do something on 3.55 or below first though :/ [14:34:33] <Mathieulh> IceKiller I just get the box to DEX, then I set the fself flag [14:34:39] <Mathieulh> so I can run fself with any control flags [14:34:49] <Mathieulh> no need for signatures [21:46:46] <Mathieulh> the exploit I have can make it so I don't need my binaries to be signed for them to run [21:46:56] <Mathieulh> including ldrs [21:46:59] <Mathieulh> or even lv0 //If we can sign are own lv0 we could get at bootloader [21:47:12] <Mathieulh> (and even update packages) [21:47:20] <Mathieulh> it's a stupid bug [21:47:23] <Mathieulh> but it's there [21:47:40] <Mathieulh> though it's a loss less convenient than just signing your binaries [21:47:45] <Mathieulh> but it works [21:48:20] <Mathieulh> it's different [21:48:50] <Mathieulh> the ecdsa code itself is secure [21:48:58] <Mathieulh> it's always been [21:49:19] <Mathieulh> the bug is even more dumb than that [21:49:29] <Mathieulh> but I am giving too many hints right now so I'll stop [21:52:56] <Mathieulh> defyboy if you want to find it, you'll have to reverse a fair amount of spu code [21:53:01] <Mathieulh> that's all I'll tell you xD [21:53:21] <Mathieulh> lol [21:53:26] <Mathieulh> it's not that easy to find though [21:53:33] <Mathieulh> sony revamped the whole appldr in 3.56 [21:53:38] <Mathieulh> and they didn't find it [21:53:47] <Mathieulh> but it's a dumb bug Source: http://ps3devwiki.com/index.php?title=User_talk:Xloader Via: PS3news.com Cette discussion est récente, elle date d'hier. Bon je vous le dit à l'avance, je ne fais que transmettre l'info donc s'il vous plait ne polluiez pas ce topic avec vos critiques à MathieuLH !!! Ce gars et même s'il ne release pas dernièrement a grandement aidé la scène PSP et PS3 durant des années. Voilà, bonne après-midi à tous le monde ici. Cordialement

oui c'est bel et bien ce montage la valeur doit être proche de 56 ohms pour que le tiroir s'ouvre et se ferme de façon correcte, tu risque d'avoir une lourdeur ou rapidité de la mobilité du tiroir. puis dans 50 % des cas, ça ne marche pas donc PCB obligatoire bonne chance

Le big BOSS de SONY vient de démentir la rumeur et dit clairement pas de PS4 lors de l'E3 2012 !! je crois même qu'on aura pas de PS4 qu'en 2014.. J'espère que microsoft fera de même Source: http://www.jeuxvideo.com/news/2012/0005572...pas-en-reve.htm

Si tu as le mode IDE, essaye avec lui si ça te donne toujours l'écran bleu, passe par ms-dos avec dosflash 2.0 pour le dump et le write le spoof et la préparation du LT plus 3.0 tu le fais sous jungle flasher v0.1.91b sous windows

utilise dosflash 2.0 plus performant et automatique pour les procédures de dump, suffit de suivre les instructions

les dumps de dosflash ne sont pas compatibles avec le Xkey si ma mémoire est bonne... ton Windows fonctionne surement en AHCI ou en RAID... bah dans ce cas, essaye d'installer windows XP ou 7 sur une autre partition sans avoir à passer en RAID ou tout simplement achète-toi un X360 USB PRO pour dumper le liteon slim via USB t'as pas de 36 solutions...désolé

Tu parles des FAT ou slim ?

vérifie sur ton BIOS que ton chipset SATA est en mode IDE et non pas en mode RAID ou AHCI une fois le lecteur détecté sur Jungle Flasher choisi slim key puis non à la question de Jungle Flasher

donc ?

Merci à vous deux !

Merci Deaphroat, je déplace en section news

si tu as un CFW avec un backup manager comme MultiMAN v02.09.02, ce dernier t'affichera la version du firmware demandé par le jeu une fois tu appuis sur la touche carreau en se plaçant au dessus du jeu sur CFW 3.55, tout les jeux jusqu'à ceux nécessitant le firmware 3.56 sont jouables c'est quoi ce jeu ?

Ok ok...ce n'est pas grave

Qui sait, cette faille utilise l'émulateur PSP alors peut être un jour on pourra créer un iso loader PSP qui utilise cette faille .. je dis ça je dis rien

ah bon...!! des liens stp nick ze trick

oui possible mais ça existe toujours sur le forum de la team xecuter certains ont dit avoir trouvé ce hitachi 0500 sur leurs slim... bah c4eva confirme encore une fois ses travaux sur le nouveau liteon 1175 [2012-01-10 02:06AM UTC] #c4e <YAGAMISVC> c4eva work very hard for LT slim New 1175 [2012-01-10 02:09AM UTC] #c4e <c4eva> <YAGAMISVC> yes c4evaspeaks.com