Swizzy

Membres
  • Compteur de contenus

    14
  • Inscription

  • Dernière visite

Messages posté(e)s par Swizzy

  1. Hello la team,

    Sais t'on si Swizzy a intégré les DGX ecc dans sa version et si il compte intégrer les patch Kv pour modder (lecteur, SN, ID, etc...) ?

    @++

    No, and no...

    DGX ecc's are pre-built, so is RGX... i might add ECC generation for those in 3.0 when ever i get the motivation to complete it... and KV modder isn't going to happen, there are certain things that you cannot modify without breaking everything... there is support for changing the DVDKey already (xeBuild feature) which is the ONLY thing you have any need to EVER change

  2. il devrait l'avoir un sur xbox newlaugh car la misère le contrôle parental sur la 360

    If it was that simple... Xbox 360 don't have a similar system with a code you supply to the microsoft tech support to bypass it, you'll instead have to read it from the NAND (i think it is stored here, not 100% sure tho)

  3. Hi Swizzy !

    It is a great honor to meet you on our forum chinese

    Yes, GX-Nand is a (very) good dumper and it's very stable unlike J-Runner.

    So, it would be great if you could integrate inside your Xebuild Gui.

    I have another interesting idea: the Deban of Nand with another kv2.

    The method is very easy and the same for all version of kernel.

    See You later crocodile !

    :ok:

    It's already supported, to really unban your console you need a clean decrypted kv, just place it in the data folder, it won't be deleted untill the gui cleans up the directory (which it does after it's built the nand to keep you from doing stupid misstakes) the file needs to have the name "kv.bin"

    Gx-Nand no GUI software :whistling: developed in Delphi and based on the reverse ingénéring the Nandpro :rolleyes:

    my src code Gx_Nand 1.8

    i'll look into the source code, once i can get it downloaded... i don't speak french so i'll have to rely on friends to download it for me, and right now it doesn't seem to work =( if someone could download it, and put it on mediafire or whatever it'd be great, something that doesn't require me to speak french or wait several hours... xD

    I already figured out that it isn't a GUI software, i just don't have time to read throught all of the squirter software to figure things out atm xD

    ** Edit: **

    Finally it worked, i've got the src now :)

  4. Downloading nand from xell is already implemented ?

    No, because it's not a reliable method, at any time the nand could be corrupted, or the transfer could be interrupted leavng you with a bad image...

    i will not add network support for anything other then maybe Simple 360 NAND Flasher when i have had some time to play with networking on Xbox 360... because then i can make a checksum before sending nand, and check the data...

  5. Sinon,

    Je confirme qu'à mon humble avis, XeBuild est le MEILLEUR outil de Hack pour l'instant.

    Encore fait des tests hier soir de dump et d'ECC sur 2 Falcon, c'est sans appel, là ou J-Runner se plante, Xebuild y va haut la main.

    Par contre, j'aurais bien aimé l'implémentation de quelques fonctions sympathiques dans XeBuild:

    - Gx-Nand (source open);

    - Emplacements et nb de dump à la demande;

    Encore merci à Swizzy si je ne l'ai pas assez dit ;)

    @++

    What exactly are you trying to say? you want me to add "Gx-Nand"? if so, where do i find it?

  6. non en faite mouflo , j'utilises toujours xebuil gui mais j'avais peur de mettre a jour le freeboot 16197 sur ma glicth , car la mise a jour de MS n'est pas encore disponible sur leur site et de plus toutes les consoles connectées sur le live n'ont pas encore eu la mise a jour donc pas que ça soit une beta la mise a jour ms que l'ont trouve sur google , c'etait pour ça ;)

    16197 is said to be final version,it is true that not everyone have it retail yet, infact i haven't seen a retail machine with it yet (by retail in this case i mean a console that is NOT in the beta program)

    My console was in the beta program, and i've had 16197 on my computer aswell since a couple of hours after it was released on live... i've noticed that i no longer have the "BETA" tab on my machine when i go online indicating it's gone final, but i haven't been able to verify that there is nothing new in the su yet, maybe there is a special one for retails? i don't know yet, the ones that are published all over the web as final are from what i know beta extracted updates...

    I only release 2.085 as an update for those wanting to build 16197 now and have a good tool for it, still working on xeBuild GUI v3, that's why there is no full corona v2 support, to much work to rebuild the functions for that in v2, i have it done in v3 already ;)

    Atm there is no need to update past 15574, there is no game that requires higher, and there won't be for another couple of months apart from maybe some xbla/dlc... but seriously... no need to update yet...

  7. bonjour,

    j'ai flashé avec la version 2.07 (tout court) et tout est ok.. j'ai pas besoin de reflasher avec la 2.071b car je vois (Fixed: There was a line to much in the retail.ini for 15574 from xeBuild, i’ve fixed it here ;) (it works etheir way but…))

    merci

    if everything works the way it's supposed to there is no need to rebuild/reflash, that change is for building retail images, which isn't even supported by default due to missing files (i don't have the new bootloaders)

    However, if you have a trinity you may want to rebuild to get xell back...

  8. If anyone get's the update i'll gladly extract it from a USB memory (all you have to do is create a USB MU using the dashboard, and without any other memory connected just connect to live, it should then ask you to download the update again, once that's done send me data0000..)

  9. Testé sur Trinity et ça a l'air de bien marcher. Ce qui est bien avec l'Interface graphique c'est que j'ai découvert pas mal d'options que je connaissais pas (la flem de lire le info.ini dodo ).

    En plus on peut gérer ses launch.ini, y a juste que quand je demande de sauvegarder le launch.ini sur la clé USB, je sais pas où il l'a mis :?

    it's stored in the root for example if you connect your USB memory device to your windows computer it would look something similar to this:

    x:\launch.ini

    where x = the drive letter that windows gives it, ussually D, E or F unless you have lot's of partitions/harddrives ;)