JPizzle

The known problem is your fuckin caps lock seems to be broken It is safe to update and there are no known issues on the new release.

FSD and RXE were merged to become F3, the new features of RxE are all in F3. Only thing missing is the skin but I think someone else released one.

it will work

Can everyone that is not getting the email please tell us which mail service they are using? eg. hotmail or gmail

The Teams behind XeBuild and Dashlaunch have released updates for their essential xbox 360 software. They have both been updated for the new dashboard update 16747 and have many more tweaks and bug fixes. For more info on Xebuild 1.12 CLICK HERE For more info on Dashlaunch 1.12 CLICK HERE

Dash Launch 3.12 ---------------- Known Issues: ---------------- - *** WARNING *** One of the testers observed a console reaching out to live despite liveblock only when fakelive or autofake was enabled. If you intend a keyvault to not get banned, do not use it on a glitch/jtag machine! - Autologin pop-up blob does not display properly... live with it. Currently the project is missing the following supported translations: Japanese, Korean, Chinese Simplified, Chinese traditional Currently supplied translations: English, French, Portuguese, Russian, Spanish, German, Italian, Polish The skin pack includes the sources used to skin dash launch as well as the string files if anyone wishes to create a translation to one of the above languages (including English, as I know my explanations are not always easy to understand.) Also included is a c# based editor for the string files to assist in translation. External fonts, background image and skins may be used by this, simply place skin.xzp and/or font.ttf and/or background.png (1020x720) beside default.xex. If neither location has a font file supplied the system font on flash will be used. ================================================================================ Overview - what it does ================================================================================ - It will launch a XeX or CON file from the path you specified in launch.ini as long as it's valid - Depending on the button you hold when the xbox is trying to load the NXE, it will divert to the xex/con tied to that button or return to default as defined in launch.ini - At boot time it is possible to subvert default item and/or NXE loading, but you must wait until the controller syncs to do so - Depending which button is held when closing miniblade in NXE (use Y button to close, release then hold a QL button) it will quick launch a CON or XEX from your ini file - allows one to patch kernel/xam at bootup with a freeBOOT patch style bin file from usb or hdd (in that order) must be in root of the device and be named "kxam.patch" and be no larger than 0x4000 bytes. Again, kxam.patch binary format is the same as a compiled freeboot patch bin, but uses real virtual addresses rather than offsets - as of 2.22 the first 32bit value must instead be the version of the kernel the patches apply to - with the included patch set, launch.xex acts as a helper to detect when xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator to function together ================================================================================ Installation ================================================================================ - have the required hacked kernel version installed on the console - get the installer to a place where you can run it, and do so. Follow onscreen instructions if any. The installer will prompt you if it needs to update the kernel/hv patches and will give you an opportunity to configure stuff. - edit the options, and dont forget to save them somewhere if you want them to be applied next boot. Don't forget to set configapp to the installer, so you can go to it any time via miniblades' system settings (hold RB to go to real system settings) - the back button is your friend if you are wondering what button to push ================================================================================ Updaters and Avatars ================================================================================ - this version of dash launch contains an update blocker that is enabled by default. There are two ways around this if you wish to install the bits and pieces used by the dash for kinect and avatars 1 - place the updater that matches this version on removable media, and rename the folder from $SystemUpdate to $$ystemUpdate ----OR---- 2 - place an ini where dash launch can find it and set the noupdater option to false - noupdater = false Updates seem to work best if memory stick is inserted while in official dash **** NOTE that some games WILL prompt you to update the console if avatars are not installed, this doesn't mean they have an update to actually put in, it just means it needs avatar/kinect bins/resources to run **** ================================================================================ LIVEblocker ================================================================================ - if you are like me, and keep your consoles off the net then this option is for you. It's capable of blocking the resolution of the LIVE specific servers and does so by default, with an additional option in the ini file it will attempt to block access to all MS servers. The default option is set up to block only LIVE servers, which still allows programs like FSD to access covers and such. The blocks lists are: weak: ^xemacs.xboxlive.com$ ^xeas.xboxlive.com$ ^xetgs.xboxlive.com$ ^xexds.xboxlive.com$ ^piflc.xboxlive.com$ ^siflc.xboxlive.com$ ^msac.xboxlive.com$ ^xlink.xboxlive.com$ ^xuacs.xboxlive.com$ ^sts.xboxlive.com$ ^xam.xboxlive.com$ ^notice.xbox.com$ ^macs.xbox.com$ ^rad.msn.com$ passport.net$ strong: xboxlive.com$ xbox.com$ nsatc.net$ microsoft.com$ passport.net$ bing.net$ msn.com$ where: somedomain.com$ = ends with somedomain.com ^somesub.somedomain = starts with somesub.somedomain ^somesub.somedomain.com$ = is exactly somesub.somedomain.com ================================================================================ Important - going to NXE ================================================================================ - if you need to go back to NXE and have default item set in ini, HOLD RB while exiting game via miniblade or exit using one of the miniblade options like family settings ================================================================================ INI notes ================================================================================ -it's possible to have multiple ini files, priority is as they appear in the list (** it is NOT recommended to launch USB con/xex from hdd ini **) the first one found on the devices in that order will be the one used at boot. -see http://code.jellycan.com/simpleini/ for more info on the ini parser ================================================================================ autoswap option functionality ================================================================================ GOD ie: disk1 = Hdd:\Content\0000000000000000\01234567\00004000\01234567890123456789; will have 01234567890123456789.data folder beside it disk2 = Hdd:\Content\0000000000000000\01234567\00004000\98765432109876543210; will have 98765432109876543210.data folder beside it EXTRACTED ie: disk1 = Hdd:\games\somegame\disk1\default.xex; disk2 = Hdd:\games\somegame\disk2\default.xex; - GOD/NXE disk rips on the same media in the same folder will automatically be found with no special naming convention - EXTRACTED games with the naming above for each disk with the disk# folders all in the same folder on the same media will be found without an ini file - swapping between disks contained on different media is not supported ================================================================================ Caveats ================================================================================ The work herein is presented as-is, any risk is solely the end users responsibility. While all of us are sorry when unforseen things happen, not every situation or mistake can be accounted for before they have been spotted. Please use responsibly. ================================================================================ Support (report bugs/request features) ================================================================================ english: http://www.realmodscene.com/index.php?/forum/14-dashlaunch/ french/english: http://homebrew-connection.org/forum/index.php?board=7.0 ================================================================================ Thanks ================================================================================ -Big thanks to those who opened the way and those who made it even more usable. -Thanks to Tux, Arbiter, stk, the2000, Corrupted, tk_saturn and Toddler for all the bugs you caught trying to sneak by -Thanks AmyGrrl for passing along the glitch and new ideas -Thanks to Tux, Ironman, JPizzle and Dionis Fernandez for helping procure a Jasper big block console to extend testing and fix NAND MU corruption bug Dionis - you went above and beyond -Thanks to vgcrepairs for providing the cygnos, dash launch likely wouldn't exist without one -Thanks to the FSD team, without your cheering this rewrite would have never been completed -Thanks to Nate and Anthony for constantly reminding me that no, I'm not alone -Thanks to FBDev and mojobojo for the data used for the patch options -Thanks to sm32 -Thanks to unknown, you know why -Extra Special thanks to SpkLeader, Boflc, and LordXBig -Big thanks to Swizzy, the least bit for debugging readmes -Thanks to XeBuild, keeping us on our toes and up to date -Greetz to XeDev and RgLoader -Thanks to Team Xecuter for thinking towards the future -Thanks to vladstudio.com for "night launch" -Thanks to Razkar for always spotting the hard to spot bugs -Thanks to Danny Lane for doing a bunch of testing on Corona 16m -Thanks Juvenal for being the best sarcastic a**hole there ever was -shouts out to E Nellie and D33per, thanks to you this is still a sourceless release ~brought to you by cOz~ //2014 ================================================================================ To Do ================================================================================ - fix hud loading of nxe rips - everything else ================================================================================ Known Bugs ================================================================================ - some well used NAND images with earlier versions of DL already installed seem incapable of being updated with larger sized files, it is recommended for the time being to make a clean NAND image with the most recent/up to date image builder if you run into this issue - nxe disk rips when launched from 16197+ metro still work, if you get an err dismiss it and launch again (it's a resource busy issue in official dash) - some situations are causing a black screen when starting installer, it somehow seems to be related to USB devices and/or signed in profiles. If you run into this issue, try the debug version of installer - it's slower because it's logging to disk but apparently works fine. - I'm sure you'll find some bugs, please see the links earlier in this doc for a place to post them where they will be seen ================================================================================ Supported Versions ================================================================================ at time of this writing, this is ONLY compatible with RETAIL kernel versions: 9199, 12611, 12625, 13146, 13599, 13604, 14699, 14717, 14719, 15574, 16197, 16202, 16203, 16537, 16547, 16747 13599 is the first glitch version supported (embedded patches) 14717 is the first glitch2 version supported (embedded patches) ================================================================================ ChangeLog ================================================================================ V3.12 - default behaviour of live block is now to use strong block rules (at least until ini is loaded) - fix compatibility issues with dashes created before AP25 was deployed (spoof the AP functions on older versions) - limit fakelive/autofake to 14717+ kernels - add export so plugins can find out where they were loaded from during dllMain() (it's volatile, copy it in Main() if you need it!) - update 16547 patches to delay network bringup in xam until launch.xex loads - add trinity internal usb to hddkeepalive (for those that have a usb hdd hooked up there) - add 16747 dash_launch_v3.12.zip

xeBuild 1.12 ============ Introduction: ============= xeBuild is a command line system image builder for JTAG, glitch, and clean images. Run the xeBuild program with no (or incorrect) arguments to see it's usage info. What's New: =========== - minor 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 xeBuild directory - on the command line type, for example: example - if you provided keys in appropriate text files xeBuild.exe -t glitch -c falcon -d myfalcon myfalconout.bin -t glitch = build a glitch type image -c falcon = use falcon bl and patch set -d myfalcon = a folder is present called "myfalcon" with per machine files, this uses it myfalconout.bin = the file that will be produced - type 'xeBuild.exe -?', 'xebuild client -?' or 'xebuild update -?' for command line info Update and Client modes: ======================== Both modes require the supported updsvr running on the xbox, full functionality may require updating console patches with the included hv patches. Both the PC and the xbox need to be on the same subnet/LAN router. Client mode is a simple way to read, write and patch flash as well as few other simple commands such as the patch updater. The patch updater will look in the folders beside the exe for {version#}\bin\patches_{type}.bin which are full patches for whichever console and hack type, it will load and strip the patches if needed and send them to the console. Note that only xebuild images are truly supported for this. Most of the client mode commands should be available on any console, even unhacked devkits. See output from 'xebuild client -?' for more information on the options available. Update mode attempts to retain as much data about the console as possible, without having to provide any info on the command line aside from optional/addon patches if required. After you copy the $SystemUpdate folder into (in this example) the folder 16203 it is capable of taking a simple command line like: xebuild update -f 16203 -a nohdmiwait It will fetch all the info from the console, and use the updater to update both the system flash and avatar data on the console (provided you have an 360 formatted HDD internally in the console.) It has some more advanced options to allow one to build the update image as well as dump the data from the console as it's acquired, while even leaving the console data untouched. See output from 'xebuild update -?' for more information on the options available. Neither update or client image writes are able to affect bad blocks, but are able to write new ones. If this happens mistakenly, an erase block command has been provided in client that will attempt to clear the bad block - use with caution though, blocks get marked as bad for good reasons and is a normal occurrence on NAND when a block becomes unreliable. With big block machines, the server will attempt to retain any NAND mu data in the system area, provided there is no system data to write in the image being sent. It's not foolproof, but update mode should not corrupt NAND mu. Example: ======== -take original console dump, put it in mytrinity folder as NANDdump.bin -set CPU key and 1BL key in ini file, verify LDV from NANDdump.bin matches console fuses if not set cfldv in ini file -build (xeBuild.exe -t glitch -d mytrinity -f 13599), flash and hopefully life is good .ini files: =========== Just a word on the format... the ini parser is not very robust, the files need to be plain ASCII, 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. Optional Patches: ================= Various optional patches are included for use with the -a option, they are: nofcrt - removes fcrt.bin requirement on some drives nohdd - disables detection of internal SATA HDD nohdmiwait - HDMI consoles will no longer wait or EXX screen when video is not ready nolan - disables wired LAN to prevent E75/76/77 on machines with a damaged PHY nointmu - disables jasper NANDmu, trinity 4G internal USB and corona 4G MMC memory units blmod.bin: ========== Changing the patches to the BL that follows the BL that is executing during glitch attempts has a direct effect on whether a machine will glitch. The provided patches are generic and work well on most machines, but this per machine build addon can now be supplied without modifying the base patches to CBB or CD via a file in the perbuild folder, they will simply be tacked onto the end of CBB or CD, and the BL size adjusted to include this new data in the hash. Keep in mind, it can take multiple attempts and re-flashing with different binary data to find something that will boot at all, let alone be more effective for your console. blmod is currently not supported by update mode. Note: ===== - 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.) Multi build/options example: ============================ when you specify -f 13599 on the command line: 13599\filelist.ini is parsed instead of data\filelist.ini Also the bin directory is used from 13599\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 13599 patch set from dash launch and other files to build freeboot 13599 example use: ------------ xeBuild -f 13599 -d myfalcon x13599out.bin -f 13599 : use .\13599\filelist.ini, and .\13599\ for firmware files, .\13599\bin\ for patches -d myfalcon : use .\myfalcon for per build files (cpu key, keyvault, security files, ini etc.) x13599out.bin: override auto generated name and produce .\x13599out.bin as the final NAND image note, if -d ***** is not specified it will still use the original /data and /bin dirs Devkit image building: ====================== This feature is currently considered Beta/Work In Progress. A new image target type was added, "-t devkit" which builds 64M flash images for devkits. Currently untested, building with a 00 filled CPU key will create a zeropaired devkit image that may allow one to boot a software bricked devkit that one does not know the CPU key for and recover it to an operational state. By powering on the console with such an image present, with a recovery DVD in the drive, the recovery software should be able to create a new keyvault, re-pair the DVD drive to the new keyvault, and allow normal operation once complete. Normal devkit image building when one does know their CPU key and thus has security files and keyvault should work as expected. Building devkit for glitch/jtag is also possible using the standard -t glitch/jtag methods. Sample ini have been provided with this release, but will not work unless patches and files are supplied. Note that devkit is not our focus, but was relatively easy and straight forward option to supply for those that wish to make use of it. jasperbigffs: ============= Those who use large block NAND are now able to nearly double the size of the system file area with this option with no apparent ill effects. Normally this option wouldn't be needed, but if one wanted to experiment with more files in flash, or one was building a devkit image for a devkit with a big block flash, this option is required. support: ======== If you've found a bug or have a suggestion, please comment at http://www.realmodscene.com/index.php?/forum/15-xebuild/ (English) http://homebrew-connection.org/forum/index.php?board=8.0 (English/French) Credits: ======== Without ikari this would not have been possible, thanks! __ ____ ___ ___ _____ / _|_ __ ___ ___| __ ) / _ \ / _ \_ _| | |_| '__/ _ \/ _ \ _ \| | | | | | || | | _| | | __/ __/ |_) | |_| | |_| || | |_| |_| \___|\___|____/ \___/ \___/ |_| [v0.10 - inspired by ikari] R.I.P. No this isn't freeboot, it is a clone and has always been since the last release of ibuild. 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! Thanks Team Xecuter for the Corona 4G! Thanks to JuggaHax, dayton360mods, glitch360team and all other contributors for helping find a way to make Corona 4G golden! Thanks to Free60, LibXenon.org, Redline99 and Tuxuser for providing xell builds <3 Thanks to Swizzy for making the official GUI front end for xeBuild, for always adding the new stuff we shovel at him and never once complaining. 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. Thanks to rgloader for doing the work yourselves, there *is* no spoon, just a glitch in the matrix. Don't believe what random people *cough* write on forums .. ----- //2014 ----- Changes: ======== 1.12 - check FCRT.bin signature with PIRS_pub.bin or MAST_pub.bin if available (selection based on content) - check DAEP signed signatures in DAE.bin (usually 2) with PIRS_pub.bin if available - check CRLP signed CRL.bin signatures with PIRS_pub.bin if available - fix mobile extraction stalling process on corrupt NAND - do not patch boot reasons into flash header for devkit and retail builds, only glitch and jtag - added patch to kernel to attempt to block network until launch.xex has loaded (if available) - add -o smcnocheck to image build options/ini; avoids fatal build error if smc is unknown - add 16747 - fixed: was not automatically creating all the folders for 16747 avatar data to be valid Use these new files with my XeBuild tutorial http://www.realmodscene.com/index.php?/topic/2205-xebuild-freeboot-nand-update-tutorial/xeBuild_1.12.zip 16747.zip common_folder.zip

Post the name of the game, the titleID and a picture of the in game system link menu

That's not cool, give credit where credit is due or I delete this thread

I was just joking swizzy

SPAM!

To clear the system cache Press the Guide button on your controller, go to Settings, and select System Settings. Select Storage or Memory. Highlight any storage device, and then press Y on your controller. (It doesn't matter which storage device you select; the cache will be cleared for all storage devices.) Select Clear System Cache. When prompted to confirm storage device maintenance, select Yes.

Those games do not have system link

just copy the content folder

check your spam folder

why wouldn't you use LiNK? Check the tutorials section for help setting it up.

You need to forward your ports manually

UPDATE F3

go into your xbox system settings in the sock MS dashboard ad make sure all your network settings are set to auto

No, it does not.

go into your FSD Setting area and enable BETA UPDATES, you will then be able to update directly from FSD

http://www.amazon.com/Wildfire-Combat-Command-Display-Wireless-Controller/dp/B0062N5FOU This is about as close to what your asking for as you will find

fake

If your console takes a bit to boot up then it is an RGH but if it boots up instantly then it is most likely a JTAG.... but if you have a SLIM console 100% it' an RGH

If you delete the plugin you will need to use the DashLaunch discswap plugin