supertintin007

aurais-tu une photo de la piste à couper? Merci

double poste

Perk List : Tier1: Scavenger -Resupply from dead bodies. pro:Extra mags when spawned. Lightweight -Faster movement pro:Climb ladders and objects faster Hardline - one less kill from killstreaks. pro: Increase Kill Streaks Damage. Healer: Faster health regeneration. pro: Reduces Flinch when shot. Bling: Allow two attachments to primary. Pro: allow 2 attachment to secondary. Tier 2: Cold Blooded: Invisable to enemy thermal, and killstreaks. Pro: no red cross-hair Marathon: Unlimited Sprint. Pro: No fall Damage Bomb Squad: Reduce Explosive damage. pro: Detect enemy explosives Overkill: Replaces secondary weapon with another primary weapon.Pro:Switch weapons faster. Sleight of hand: Faster Reload Time. pro: Faster ADS to all weapons including Sniper rifles. Tier 3: Ninja: Silent movement. Pro:Invisable to hearbeat sensor Tactical mask: Reduce Effect of Flash and stun. Pro: Reveal the position of a flashed or stunned enemy Steady Aim -Increase hip-fire accuracy. pro: longer breath aiming down a sniperor thermal scope Scrambler: Jam enemy radar and delays enemy claymore explosions. Pro: Electronics are all disabled in the radius of the player."Emp Effect in the radius". Quick Reflex: Faster Melee recovery and faster throwing speed of lethal and secondary grenades. Pro:Quicker aiming after sprinting. Killstreaks : Non Stackable 3) Mortar Team (1 location) 3) UAV 4) Counter UAV 4) SAM Turret 4) Care Package 5) Precision Air Strike 5) Sentry Gun 6) Artillery (3 location) 6) PredatorMissle 7) Attack Helicopter 7) Stealth Bomber 8.) Harrier Airstrike 8.) GlobalHawk (blackbird effect) 9) Fire Scout UAV (uav + attackhelicopter effect) 9) Pavelow 9) Emerygency airdrop (4 Package) 11) EMP (last for 60 sec) 13) AC130 15) Chopper Gunner 18) Nuclear EMP (Disable Perks for opponent team for 30sec only, Eletronics and Air Killstreaks wont be destoryed.) 25) Tatical Nuke

Les 39 pages trop lourd pour envoyer par mail

EASY CB TEST 1.1 pour vérifier si le CB est compatible JTAG, dans le doute biensur

Bon je reviens aux nouvelles : apparement, ils seraient parvenu a spoofer le un dash 12625 par un 9199 et jouer en ligne... si j'ai bien compris car 39 pages... Pour celui que cela interresserait, je possède ces 39pages. envoyer un mp avec votre mail et je vous les renvois. ps: dsl pour l'info tardive mais je n'avais plus d'acces en prenium

https://bf3alpha.battlefield.com/index.php?id=1

+1 un grand merci pour ton retour d'infos SoulHaven

oui tout à fai!t je crois que c'est à partir 1500 messages que tu deviens vip

intéressant lol moi je suis VIP ps : à l'après de 3 jour, on a la même date d'inscription

nfo complète : fbBuild 0.32 ============ Introduction: ============= Sad to hear the rumor of ikari stepping down, and even sadder to hear of the profiteers taking advantage of this... we bring you a tribute to ikari. If you paid for this, get a refund! fbBuild is a NAND image builder made to suit freeBoot style images, the included patches and freboot.bin core are based on the original works done by ikari. It is suitable to build rebooter images for all current JTAG exploit compatible xbox 360's. As with ibuild produced images, this version only requires a single flash 16MiB in size or larger. What's New: =========== - detect and optionally retain NAND MU data in 64 and 256/512M dumps - optionally configure which power on button starts xell - bug fixes Current Limitations: ==================== - STAY THE HELL OFF LIVE! Nuff said, we're not you're mum. How To Use: =========== - See individual folders for lists of files to provide - if desired provide replacement cpu and 1bl keys in text files - open a command window in the fbBuild directory - on the command line type, for example: example - if you provided keys in appropriate text files fbbuild.exe -c falcon -d myfalcon myfalconout.bin -c falcon = use falcon bl and patch set -d myfalcon = a folder is present called "myfalcon" with per machine files myfalconout.bin = the file that will be produced - type fbbuild.exe -? for command line info Block Remapping & nanddump.bin: =============================== First, don't expect the method used to be perfect for every dump. The idea is, if you have a working JTAG you can dump it's current NAND by running something like Flash360 on it and the final freeboot image that is produced will mirror any existing remappings. Also, fbbuild should be able to take your current smc.bin, kv.bin and smc_config.bin straight from the dump (external files overrule/replace ones in the dump) provided it can decrypt them when needed. Most original.bin dumps using hardware methods will also produce usable remappings as well, with the exception of bad dumps which may produce some unusual issues with default settings. Corrupt or incomplete dumps will turn up a lot of unusual errors, the option "noecdremap" was added to work around such issues, and the option "noremap" was added so that a dump can be used to aquire smc.bin, smc config and keyvault without applying any remaps to the final image. .ini files: =========== Just a word on the format... the ini parser is not very robust, the files need to be plain ACII, everything after a ; on a line is ignored, and spaces are not acceptable (they get removed). Things like CPU key and 1BL key, if present in the per box ini file need not be placed anywhere else. Note: ===== - for those of you using donor data, the security files shouldn't pose a problem but make sure the CPU key you use is from the machine that donated the kv instead of the target machine you are building the image for. - DON'T USE THIS UNLESS YOU KNOW FOR SURE THAT YOU NEED IT! Using an incorrect controller config can result in problems remapping bad blocks (even manually.) If you have a 16M jasper, an additional build type has been added 'jaspersb', by default the image will be built for jasper with big block controller (config 00023010), use this alternate switch to build for small block controller (config 01198010.) - the /bin and /data folders are legacy folders from ibuild's format, they are not required or recommended. Multi build/options example: ============================ when you specify -f 9199 on the command line: 9199\filelist.ini is parsed instead of data\filelist.ini Also the bin directory is used from 9199\bin\ instead of bin\ allowing anyone to create multiple builds without multiple instances or rebuilds/hex edits/hacks of the main app. The example provided is the last version of 9199 patch set from dash launch and other files to build freeboot 9199 example use: ------------ fbbuild -c xenon -f 9199 -d myxenon x9199out.bin -o nodvd -o cygnos -c xenon : specifies xenon patchset and bootloaders -f 9199 : use .\9199\filelist.ini, and .\9199\ for firmware files, .\9199\bin\ for rebooter files -d myxenon : use .\myxenon for per build files (cpu key, keyvault, security files etc.) -o nodvd : uses alternate tray check in bootstrap for those with problems with default one -o cygnos : sets UART speed to cygnos compatible in bootstrap x9199out.bin: override auto generated name and produce .\x9199out.bin as the final NAND image note, if -d ***** is not specified it will still use the original /data and /bin dirs Credits: ======== Without ikari this would not have been possible, thanks! __ ____ ___ ___ _____ / _|_ __ ___ ___| __ ) / _ \ / _ \_ _| | |_| '__/ _ \/ _ \ _ \| | | | | | || | | _| | | __/ __/ |_) | |_| | |_| || | |_| |_| \___|\___|____/ \___/ \___/ |_| [v0.07 - inspired by ikari] R.I.P. Thanks and greetz to everyone who has contributed to hacking this wonderful machine. Thanks to the engineers and countless others who made the machine what it is... we only wish they had listened and RROD was not a problem. If we were to list everyone here, there would be no time left to play on the machine! Big thanks to the folks at #freeboot on efnet for the tireless hours of help you all give freely. Thanks to the testers who tirelessly made sure stuff worked. Don't believe what random people *cough* write on forums .. ----- 2011/19/07 ----- Changes: ======== 0.32 - fixed yet another bug in the ini parser (affected lhelper.xex integration) - corrected bad block detection bug on large block dumps (nandmu) - correct mobile dat extraction on small block dumps for big block controllers - corrected wording (oops!) of ECD option in ini sample file - added option to ini file to try to retain NAND MU data on big block machines - added option to ini file to set which power-on reason starts xell when not using oldvd/nodvd - -v messages are now automatically logged to a file regardless of specifying -v on command line - core and ini updated to allow specifying a power reason to cause dual NAND !SWITCH command - add 13599

désolé c'est ok

suffit d'utliser ces originaux pour ces titres... c'est pas la mort... vive l'arrivee du xkey et de bon tests pour être sur du "gadget" lol

*console fat liteon flashée lt+1.1 connectée au live non flaggée : erreur lors de la mise à jour avec le code erreur => soluce: reflashe en lt+1.9 mise à jour faite à 100% *console fat liteon flashée lt+1.9 connectée au live non flaggée : mise à jour appliquée sans code d'erreur

à partir du moment où tu es sûre de ton montage, de tes diodes ou résitances utilisées (fonctionnelles) : oui cela ma posé problème avec quelques consoles (e79, console qui ne démare pas etc) et cela à fonctionné dans certain cas en mettant à jour vers dash supérieur. Jai constaté ces anomalies à l'arrivée des premiers freeboot, par contre pas problème avec les xbr encore une fois ce n'est que mon expérience personnelle, c'est une voie a testé

1. tu mets a jour ton dash avec le dernier compatible JTAG min 73XX ou max 77xx pas plus sinon tu bouches la faille. 2. tu redumps ta nand (2x) 3. tu installes xell, pas xellous avec JTAG Tools 4. tu recupères la clé 5. tu utlises easy freeboot 5.3 ps : pourquoi mettre à jour car dans mon expérience personnel dans l'installe de jtag, j'ai eu plein de problèmes similaires avec des vieux dash pour passer en freeboot. En mettant a jour avec le dernier compatible JTAG, c'est passé nickel. si cela peux t'aider.

c'est destiné à Bo en beta et le lancement officielle se fera sur mw3

tournes toi vers une hybrid (essence-electrique)

remplaces les diodes si tu es sûr de ton flash car cela m'est déja arrivé qu'une diode lâche après plusieurs tentatives de flash pour quelle raison je l'ignore...

This tutorial is for the "repair" of JTAG Tool for use with the most common setup. coolshrimp changed JTAG Tool in 3.00 to an awkward stance where it is undesirable for me, among many others. This fix will allow you to use the DB1F1 and aud_clamp SMC as the alternative, as well as removal of KV hash check encryption to use a non-matching KV with your NAND. If you have questions, feel free to reply in this thread. Let's begin. Download this file. This .rar contains the modified files necessary for this tutorial. Open and extract the containing files. Open the directory for JTAG Tool. This is default under Computer > Program Files (x86) > JTAG Tool. Delete the XeLL Bins and the Dash folders. Move the two folders that you extracted (Dash and XeLL Bins) into the JTAG Tool directory. Once completed, you will see the new folders in the directory. That's all there is to it! Using the alternate is even easier. Just select the motherboard you are working with, click the little wrench under "Settings", open the Drivers/Options tab, and change the SMC points to "Aud_Clamp & DVD_Tray". This is now the modified SMC for DB1F1 and Aud_clamp. The KV hash check removal is already included in all HDMI console NANDs built using the freeBOOT maker within JTAG Tool. Please leave your feedback on anything I can change. Hopefully coolshrimp will fix this so we don't have to deal with modifying his program to work the way we want it! Thanks to: E Nellie for his Hex for KV hash check removal coolshrimp for JTAG Tool Merci à iMoses pour le tuto

voici l'historique de toute les attaques connues envers sony ici

le jeux 52€ + l'abonnement à mw3 60€ + l'abonnement au live 35€ = ca fait chers le jeu ... de plus avec un moteur même évolué... et j'en passe

Bonjour à tous, Opening Cup 1on1 Première compétition sur DiRT 3, l'Opening Cup en mode Rally ! Vous pouvez retrouver toutes les caractéristiques de ce Tournoi ci-dessous ou ici: Mode de Jeu : Course Rally Voiture : Série Circuit : Au choix Météo : Libre Nombre de tours : 3

Citation (Pikakat @ 16-05-2011, 16:38) salut a tous j'aurais une petite question, j'ai preco mon x360key ici mais ils annoncent une dispo mi-juillet, pensez vous que le delais sera respecté, je me rapel encore des cle ps3 (team ps3jaibreak) et leurs dates à rallonges.. peut ton faire confiance a wiikey ?! merci Commander sur de telle site faut vraiment le vouloir .alors soit tu nous fait une pub deguise pour ton 1 message ou soit tu ne connais pas les grand sites de vente ce que je doute. site sérieux! de plus c'est un membre de notre forum!

un rebooter 12646 est déja fonctionnel mais pas encore distribuer