the-green

si je peux t'aider un peu, il existe un ancien document pdf intéressant, il porte le nom de XBOX 360 pour les nuls edition Hiver 2009 il regroupe toutes les avancées du hack 360 jusqu'à 2009 sur ce document j'ai vu des topics qui parlent de la programmation en externe des mémoires des lecteurs Hitachi, il y a aussi des liens utiles vers des tutos anglo-saxons à ce propos edit: tiens le voici ici: http://www.multiupload.com/IT6HT2FNK5 source: http://gueux-forum.net/index.php?showtopic=176625

...lol il te faut une PS3 pour adorer la marque !! Une chose est sur sur la scène PS3, c4eva est nettement meilleur que tout les développeurs de la scène Ps3 confondus .

Mais chamin, à part faire ça pour le plaisir je ne vois pas pourquoi tu veux récupérer ce Hitachi !!! les anciennes XENON n'ont pas d'OSIG, tu peux mettre n'importe quel lecteur à la place !

ces photos sont uploadés sur serveur ftp de GX-Mod, les photos sont tous cliquables, essayes en cliquant sur une des photos

http://www.truebluejb2.com/patches.html but it's not up to date

essaye de les convertir (google eboot to iso/cso)

Oui je crois que l'eboot spyro 3.55 TB existe oui la plupart des jeux compatibles TB fonctionnent en extranet ou en interne

un tuto par ici http://iphonetweak.fr/2011/12/27/comment-j...n-untethered-a4

oui ça vient de sortir, tiens un lien vers un tuto: http://iphonetweak.fr/2011/12/27/comment-j...n-untethered-a4

La team Cobra ne connait pas le repos, elle fait toujours de son mieux pour améliorer le support et les fonctionnalités de son dongle Cobra USB. Dans ce sens la team nous livre aujourd'hui une nouvelle version de leur fameux multiman Cobra Manager, une version qui porte le numéro 03.01.03. En tete de nouveautés que des améliorations de l'émulation PSP, avec surtout le support des images compressés cso de vos jeux PSP. Les jaquettes PSX/PS2 voient leur nombre aussi s'élever à presque 6500 jaquettes. Nouveautés/Corrections: Added support to extract PSP CSO (compressed ISO) files in File Manager (extracted image is saved in /dev_hdd0/PSPISO) Added support to show and extract PSP CSO files in XMMB/XBDM display modes (Retro column) Added support for loading PSP ISO and extracting PSP CSO from USB connected PSP (MemoryStick MS:/ISO folder) Added shortcut to ISO folder when browsing external USB devices (PSP connected with memory stick /ISO folder, containing CSO and ISO files) Added support for loading PSP CSO (CSO will be extracted to ISO and saved in /dev_hdd0/PSPISO before loading) Added music playback fade-out when leaving mmCM Added couple of themes in the Web/Download themes menu Changed displaying of PSP game titles in Retro column when game name match is found in local database Added new PSP game names to local database (now over 700) Updated online PS1/PS2/PS3 covers to 6558 total: 3147 PS3 covers and 3411 PS1/PS2 covers Lien de téléchargement sur le site officiel: http://www.cobra-usb.com/ Source: http://www.ps3crunch.net/

+1, le CFW kmeaw reste largement suffisant le CFW rebug 3.55.2 a certes plus de fonctionalités/options mais en matière de backups PS3, rien de plus, rien ! le CFW rogero V2 est un kmeaw avec un spoof version 3.72, il est utile surtout pour le downgrade depuis les OFW 3.6+/3.7+ ! prends le CFW kmeaw 3.55

A la place de deux résistances-là met une seule de 56 ohms ou deux successives de telle sorte que t'aura 56 Ohms ça marche un fois sur deux ! si ça passe pas, remplacement de PCB obligatoire

OK, merci Enzo

regardez cette photo ! Oups corrigé Source Crash Serious sur son Twitter http://twitter.com/#!/CrashSerious

tu as testé le hack kamikaze ? si oui tu as surement touché la mauvaise piste dans le chip lors du perçage ! bon il y a une pseudo solution avec un pont à faire en utilisant un fil et une résistance 56 ohms, ça marche qq fois, il y a des photos la dessus, cherche un peu Si ça marche pas, tu sera obligé de changer de PCB par celle de la team xecuter ou celle de la team matrix

La team jungle nous livre une nouvelle version de leur logiciel de flash des lecteurs XBOX 360, bien sur vous pouvez le deviner, la nouveauté est le support des deux derniers firmwares sortis, à savoir le LT plus 3.0 benq et liteon FAT Support for LT Plus 3.0 -Lite-on Phat 02510C -Benq 04421C Source: http://jungleflasher.net/191.html

Ce gars a une certaine méthode pour décrypter ces eboot 3.6+, mais je ne sais pas s'il veut vraiment la lâcher ou non la traduction de ps3news me parait celle de google translate, c'ets pour ça qu'elle est difficile à comprendre

Non, non, tkt pas c'ets intéressant, justement je voualis savoir comment a-t-il fait pour décrypter ces deux eboot 3.6+, merci, bah le voici le texte en totalité According to chnps3hax the author of HOD: Overkill 3.55 / 3.41 fix has explained the cracking process in this way: bbs.duowan.com/viewthread.php?tid=21824399&page=1#pid233070436 Talk about those broken things break 3.7 First of all I want to say that they are not a big God, no previous 3.41 3.55 crack, I simply can not successfully decrypt a eboot. Second, why this is the House of the Dead and the U.S. version. This is entirely a coincidence that this series for a long time I play the arcade, can be considered a meal. Abroad, a friend sent me a new ps3 for, so this is the only hand I have some 3.60 or more games. So I only studied this. On the information I have run, jb2 the hack and I may be very similar, The only difference is that they decrypted elf after the implantation of his own to make the offset only to start an electronic dongle. And I do not have spare time, so be honest I get hold of another electronic one I can not make enough to sell such a thing. Second, I have limited knowledge of electronics hardware can not make such a thing. Talk about the high version of the game crack, 3.6 and 3.7 of the runtime is not much difference between 355. There was no increase in any application layer interface, of course, which in fact break the api and nothing to do. Analogy, the first ps3 library does not move this thing, so you want to move the game to run on a 1.0 system is impossible. Why say the above, I just want to say the sdk cable X offers no real effect on the crack. However, there is a complete development of the sdk contains the firmware, this thing of autonomous systems research has a considerable degree of help rebug system resulting. Also said a lot of nonsense, is that people are concerned about cracking method. Decrypt the game I generally have one week to engage in a lot of trouble. Not to say that this game trouble, but 3.6 + is the underlying key trouble. Thus, although ultimately I succeeded to get the desired non-encrypted elf. However, we do not want to imagine, as long as the cgwin knock a few lines under the command over. Results in hand and code are not collated, very chaotic. Theoretically you can do to step in a new unself.exe get elf. However, before the light offset even get me those head. I will have time to make tools, but this is not one or two days on end, she says. In addition, I also need to verify the versatility of this hack, because I am not so tall version of the game. Not like I do not bother to buy and the next. 3.7 Following the game, but in theory should be no problem. JB2 the release of very slow crack the game, I think they did not find very effective method is similar to human flesh so to change the practice of offsets in the lane. So please do not request a specific message or post crack method. First, I can not explain clearly, and second, that ugly, I know you do not necessarily free to write, so I would rather save the time to write this tool. On cfw, I just want to say this more than 3.6 and 3.55 firmware is completely different. Not so easy to put things inside the embedded system to the self-made, I would like to study crack ps everyone knows. Take a look at some foreign authors, they should also upset with this issue. Of course, foreigners dumped my skills are definitely a good few blocks, I used to be a self-made system gives as good as I made sets of rocket to Mars. We often talk about the last mentioned sprayer. Spray does not spray for me does not matter, because even my own hair after I posted do not necessarily see, I even saw the heart in addition to criticize a SB next second I forgot. As for after the game, I think I will organize things on hand, Of course, not to say that I will not engage in, I just want to say my time is limited. Finally, the last, I do not want to break anything to ensure that the next game, I can only assure you I would not want to go to make money as jb2. Because crack is just playing for me, today, the more interested in the play, not interested in the day I do not want to play. There is something that everyone on the forum I agree, I do not liquidzigong then God, I do not want him to become the second, so we do not be too flattering. 1) he has done this 1 eboot for a week 2) he has trouble to find "low level key" of 3.6+ 3) he finally got the decrypted elf 4) the theory of unself.exe can be used, except he has to manually calculated the offset address 5) he said, 3.6+ is decrypted in this way , and so as the 3.7+ 6) he suspect the JB2 team is using the similar method , especially the "manual calculated offset address", so that is why JB2 release the game so slow. on the other hand, see the post #15 (bbs.duowan.com/viewthread.php?tid=21824531&page=1#pid233176672), #88 (bbs.duowan.com/viewthread.php?tid=21824531&page=6#pid233632785), the author mentioned: In fact, I now do not want to talk too much about the specific methods, because the other posts have said, do not want to install too many things to b but finishing. But since I put the offer under their own ideas. The original crack was there before the title key obtained elf, and then re-encrypt the signature look into eboot.bin offset change while the system version. However, even with 3.7 key, because Sony changed the base system, not the original unself same elf. Therefore, we may wish to change thinking, we change the retail direct signature bin, into a development with a fake signature, so that together with unself or unfself can also get what we want, which is elf file. Almost walked on the surface of the road, but in fact they successfully bypass the firmware mechanism of change, more importantly, from retail to a devkit only need to change the signature part of the key but not all. Of course not able to do to change the key signature, in theory, can be a new unself to get the elf, but then again it takes time, so it might as well find a shift in the original eboot in more direct. Finally, one thing is to open is no essential difference between 3.6 and 3.7, to be broken break on all Sony just threw a vest out of it more. JB2's do not read unself eboot can not unlock after make_fself can run. Today, the time to find a few of their crack look inside the devkit signature and real development of the signature is not an ordinary thing for a while. It means this part by their own re-encryption algorithm, which must be with the electronic part of the dongle. If there is no usb electronic dongle, the eboot is illegal in terms of machine procedures, 100% 800XXX error. But they eboot from several of view. Algorithms seem to be the same, take the time to put this into a normal offset fxck signature devkit should be able to run all the machines. But people like jb die I will definitely pumping, or at least non-aggression is the basic bottom line. I do not care nothing greetings, But I do not want those people to spend money to buy a jb2 greeting my family. Also add the meat under the offset for the people, of course, not just open your hex stuff in it one by one change, I mean borrow lv1 and 2 of the key results to a large segment of the for. Final point is that foreign hackers before a lv0 get permission, I just want to say if it is true that he is God, At least now I have no idea of ​​that. jb2 the hands of those people should not lv0 results. Otherwise, the system should be made up almost settled. To the busy end of things, but I have found in the study npdrm and somewhat, there is I hate SE cancer, but like it enough to install FF b, the other not much to say, you understand. 1) he used lvl1 & 2 key to replace the code inside eboot.bin. 2) and he said he doesn't need the lvl0. 3) he changed the eboot from retail to dev 4) to do that , he need to calculate the key. 5) finally he double confirmed 3.6+ , 3.7+ are the same and so the jailbreak method although i don't really understand what the author say, but i hope this thread could help people who want to do the same as the author.

oui t'as raison

c'est clair, allez qui vivra verra ça reste toutefois dommage que personne ne pense à faciliter un peu plus ou de trouver des solutions plus simples et moins risquées aux liteon slim Winbond,

Arriver tardivement est mieux que ne jamais arriver La team Maximus restera malgré tout au top par sa créativité, franchement je n'ai jamais aimé leur idée de fileset, ils auraient mieux laisser leurs clients utiliser le pack de firmware habituel lâché par c4eva, comme ça les clients ne vont pas venir se plaindre du retard à chaque fois

ce sont quoi ces fichiers eboot ?? des jeux ??

il faut patcher le backup iso de ton original avec le patch topology data disponible ici http://gueux-forum.net/index.php?showtopic=264083 il faut utiliser le Xbox backup creator v2.9 build 350 pour appliquer le patch (section news pour le trouver) puis re-graver ton jeu correctement avec un liteon iHAS B en fw burner max de c4eva et des verbatims, la gravure avec imgburn 2.5.6.0 voilà l'histoire en totalité

pour le liteon, oui le probe V3 va suffire largement le benq fat est le lecteur XBOX 360 le plus facile à dumper/flasher, avec jungle flasher et un chip sata compatible ou x360 usb pro, ça prend normalement 50 secondes, oui 50 secondes. tiens ce tuto, c'ets toujours la même démarche, dump/spoof avec le LT plus 3.0 puis write http://gueux-forum.net/index.php?showtopic=256974 Pour le lecteur Hitachi, c'est un peu variable seon la version du lecteur (32, 34, 40, 58, 59, 78 ou 79) mais c'est toujours simple, s'il est dèja flashé il faut le remettre en OFW avant de lui passer le LT plus 2.0 s'il s'agit d'un hitachi 78 ou 79 surtout ne pas faire la MAJ 14699 car elle bloque la lecture des XGD3, il faut attendre le LT plus 3.0 pour ces lecteurs j'ai un tuto pour le hitachi 79 en cas de besoin (4 ème page en arrière dans la section tuto à publier)

Il te faut un graveur liteon iHAS 124B