cory1492

Moderators
  • Content count

    46
  • Joined

  • Last visited

  • Days Won

    4

cory1492 last won the day on June 15 2014

cory1492 had the most liked content!

Community Reputation

22 Excellent

About cory1492

  • Rank
    TeamFSD
  • Birthday 09/29/77

Profile Information

  • Gender
    Male
  • Location
    I'm right here dude.. no your other here!
  • Interests
    I like things, and stuff, and stuff with things in it.

Recent Profile Visitors

213 profile views
  1. Just in case you don't know... xebuild does not use FTP to do updates, are you running either a recent version of the dash launch installer or the (standalone) update server on the console at the time you try this? If you are using dash launch installer, have you disabled update server in the dash launch options? If there is a firewall, update server sends a UDP beacon on port 48 (not needed if you force the IP address), and xebuild will establish a TCP connection on port 49. Also, a quick way to see if xebuild is seeing the update server beacon (instead of forcing the IP) is simply: xebuild client -i
  2. Whether or not the title space is rebooted when you eject the tray comes down to a flag in the currently running title. Titles such as aurora, official dash or even xexmenu have this flag set so they don't exit when you eject the disk tray - its even possible titles from the marketplace (GoD or XBLA) may have this flag added. All said though, nxe installs were designed to use the disk still (mostly to verify 1disk to 1console installs, as well as give AP2.5 responses) so ejecting the disk would in effect deauth the nxe install, and iso2god are basically the same thing that is on the disk but nothing really tells the game that it is not on a disk so it would act like a disk. Any which way you cut it though, unless the installed game specifically is set to ignore disk tray eject its going to exit when you eject the tray - this is by design in the OS. Dash launch is a great place to solve such minor annoyances, perhaps this flag can be spoofed on any title that isn't running from a disk (but at the risk of breaking things like autoplay on disk insert.)
  3. Wired controllers also do not show shuttemps.
  4. xeBuild 1.11============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 fixesCurrent 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 infoUpdate 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#}binpatches_{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 unitsblmod.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: 13599filelist.ini is parsed instead of datafilelist.ini Also the bin directory is used from 13599bin 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 .13599filelist.ini, and .13599 for firmware files, .13599bin 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 dirsDevkit 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.11- fix a bug which caused an infinite loop when a mobile*.dat was smaller than 512 bytes - Foo you too mobileE.dat! (thanks blakcat!) xeBuild_1.11.zip
  5. See http://www.realmodscene.com/index.php?/topic/2924-dashlaunch-311/
  6. V3.11- more thoroughly check display names in xcontent header if english name is not present (TODO: check if this applies on launch items too)- yet another correction to the dev kernel checks (thanks tydye and XDK!)- add 16547- fix autoswap for going from disk 2 to 1 (DS3) (thanks c.... and Swizzy for the report!)- made launcher mode useful if dl is not running dash_launch_v3.11.zip
  7. xeBuild 1.10============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 - add 16547Current 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 infoUpdate 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#}binpatches_{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 unitsblmod.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: 13599filelist.ini is parsed instead of datafilelist.ini Also the bin directory is used from 13599bin 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 .13599filelist.ini, and .13599 for firmware files, .13599bin 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 dirsDevkit 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.10- add 16547- fix a bug with build mode mobile*.dat extraction when multiples of the same settings are stored in the same block but version number does not increase- minor fixes xeBuild_1.10.zip
  8. definitely definitely, yeah.
  9. from a more reliable source:
  10. The AC4 issues seem to only occur when using an extracted iso? Is this true for you torrne666? Guilherme: Not much we can do as no one in the testing group has had any issues with black screens even on the previous builds, especially if those of you who actually still have a black screen issue ignore the debug build... it's not a tiny code base where it comes to the installer, "it dun werk" just doesn't cut it to narrow down where exactly the issue is or even could be if we can't reproduce the problem. As to the ethernet polling fix in this version, it was a guess implemented based on only the information "disconnecting LAN cable prevented the issue" where a bit of code would incessantly poll for the network address until it got one; a delay was added between unsuccessful checks and a limit to the number of times it would check meaning at most it would hang it for a second or two if getting the address was the issue.
  11. <cough> DL 3.10 readme (note the bold underlined part emphasized here): <cough> That said, unless they are doing some voodoo to the kernel version info in RGLoader (afaik they are not) DL installer should be telling you that devkit fw is not supported at all.
  12. Do you have the update server running? IIRC update server doesn't have this fix yet. (It's far fetched, but we don't see any way to reproduce it otherwise.)
  13. This is the default one that is included in the install package of dash launch as "info_launch.ini" ; launch.xex V3.0 config file; parsed by simpleIni http://code.jellycan.com/simpleini/; currently supported devices and paths:; internal hard disk Hdd:; usb memory stick Usb:; memory unit Mu:; USB memory unit UsbMu:; big block NAND mu FlashMu:; internal slim 4G mu IntMu:; internal corona 4g mu MmcMu:; CD/DVD Dvd: (not recommended to use this one); buttons can point to any xex, or any CON with default.xex in it on any of the above devices; note that Right Bumper is ALWAYS default to return NXE; if you want to assign an additional one, use the path Sfc:dash.xex ie:; BUT_A = Sfc:dash.xex; all comments and fields in this file are optional, you can remove anything you don't need; sorry for any double negatives ; njoy, cOz; example entry; Default = Hdd:FreeStyledefault.xex[Paths]BUT_A = BUT_B = BUT_X = BUT_Y = Start = Back = LBump = RThumb=LThumb=; Default is what loads when you hold no buttons; leave this blank if you want NXE as defaultDefault = ; at boot time, default can be overridden based on how the console is turned on; if you start with wired/wireless/IR guide button, this item if existing will be used instead of default; note that the Guide item is ALWAYS overridden by option: remotenxe = trueGuide = ; if you power on with the button on the front of the console (or the power button on a remote if remotenxe is not set to true); this item will be used instead of defaultPower = ; if set, going to system settings from HUD will run this app, override with Right BumperConfigapp =; if set, this will be run as a title before any other option occurs, does not get circumvented by held buttons or default; guide/power opts are processed after this; intended for a short video player to allow replacing bootanimFakeanim = ; by default this only dumps to UART, setting a file here will cause unhandled exception info to be dumped; as text to a file. Same path restraints as the quick launch buttons.; if exchandler is set to false, this option does nothing.; note that this uses the first drive of the class found, so if you use usb: and have more than one usb device; it may wind up on any of the usb devices depending on which was enumerated first. The path for the file is only; checked on boot, so the device must be present at power on and at crash time for this to be effective; ie: dumpfile = Usb:crashlog.txtDumpfile = ; example plugin entry; plugin1 = Usb:pluginaplugin.xex[Plugins]plugin1 = plugin2 = plugin3 = plugin4 = plugin5 = ; these options are never used directly by dash launch but serve to give the configuration program; a place to keep these values; note that things like ftp and upd servers are only running while installer is running[Externals]; if true, the configuration application will start a FTP server (user/pass: xbox); if not present default is FALSEftpserv = false; if ftpserv is true, this is the port that will be used by the FTP server; if not present default is 21ftpport = 21; if true, the configuration application will start the xebuild update server; if not present default is FALSEupdserv = false; if true, the configuration application will start in launch mode instead of options mode; if not present default is FALSEcalaunch = false; if true, temps in installer and in guide (shuttemps option) will be shown in fahrenheit instead of celsius; if not present default is FALSEfahrenheit = false[Settings]; if true, brining up miniblade in NXE and then pressing Y will cause launch.xex to relaunch for you; note you must release Y button then press desired QuickLaunchButtons after or use default item; if not present default is TRUEnxemini = true; if true ping limit will be removed for system link play (thanks FBDev!); if not present default is FALSEpingpatch = false; if true (most) xbla will no longer need yaris patching (thanks mojobojo!); if not present default is FALSEcontpatch = false; Normally when a fatal error occurs the xbox will just freeze, setting this to false will cause a reboot or powerdown; setting to TRUE will also disable the unhandled exception filter which tries to intercept recoverable unhandled exceptions with exit to dash; if not present default is FALSEfatalfreeze = false; when fatalfreeze is set to false, setting this to true will cause the box to reboot, setting it to false will instead have the box shut down; note that this option does NOTHING when fatalfreeze is set to true; if not present default is FALSEfatalreboot = false; setting this to true will cause the box to reboot (soft reboot) the way it was intended to; on jtag ONLY set this to true if using blackaddr's reboot fix for SMC, else on reboot you will get E71 and corrupted dash/video/etc settings; if not present default is TRUEsafereboot = true; when set to true, it is possible to hold RB when launching a game to have the region that the game gets from xam spoofed; if not present this is set to FALSEregionspoof = false; when regionspoof is true, you set your region here in hex preceding the value with 0x, for examle devkit would be region = 0x7fff; if not present but regionspoof is set to true, this is set to 0x7FFFregion = 0x7FFF; when set to false, ejecting a dvd video or game returns you to your default item, set to true to auto exit to NXE; if not present this is set to FALSEdvdexitdash = false; when set to false, using the exit item in an XBLA game returns you to your default item, set to true to exit to NXE arcade menu; if not present this is set to FALSExblaexitdash = false; when set to true, using miniblades system setting options will not exit to NXE; if not present this is set to FALSEnosysexit = false; when set to true, miniblades will not appear... ever (requested as child saftey measure); note that using this option overrides everything in dash launch that relies on miniblade exits to function; if not present this is set to FALSEnohud = false; when set to false, xbox will be capable of finding system updaters; if not present this is set to TRUEnoupdater = true; when set to true, dash launch will put all debug strings out to uart; if not present this is set to FALSEdebugout = false; when set to false, dash launch will not attempt to handle last chance unhandled exceptions; if set to false, exceptions will also not be dumped to the dumpfile; if not present this is set to TRUEexchandler = true; if set to true, this will block the console from resolving LIVE related dns; if not set this value will be TRUEliveblock = true; if liveblock is set to true, this will block the console from resolving all MS related dns; setting this to TRUE will also block apps like freestyle from accessing things like cover images; *** note that if NO INI is present for launch.xex, this is set to TRUE; if not set this value will be FALSElivestrong = false; when set to TRUE the X (guide) and power button on IR remotes will cause the xbox to boot to NXE instead of default item; note that powering on with the windows/start button automatically goes to NXE's media center now regardless of how this is set; if not set this value will be FALSEremotenxe = false; when set to TRUE all USB drives will be polled at hddtimer intervals for the file "alive.txt" in their root; if the file exists, it will be recreated and 16 random bytes written to it on each poll which should keep drives from spinning down; if not set this value will be FALSEhddalive = false; in seconds, the interval between when USB devices will be polled for "alive.txt" file; if not set and hddalive is set to TRUE this value will be 210hddtimer = 210; attempts to disable popups related to signing in, like "live is blocked" and similar; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S A LOGIN DIALOG MAY NOT BE PERFECT !!; !! to sign into live profiles other than auto signing on boot you MUST accept the 'check live for updates' dialog BEFORE enabling this option !!; if not set this value will be FALSEsignnotice = false; when you hold guide button to shut down xbox, normally the 'cancel' option is selected; setting this to TRUE will cause the shutdown option to be auto selected instead; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S SHUTDOWN DIALOG MAY NOT BE PERFECT !!; if not set this value will be FALSEautoshut = false; when you hold guide button to shut down xbox, normally a dialog comes up; setting this to TRUE will cause the console to shutdown instead of show a dialog; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S SHUTDOWN DIALOG MAY NOT BE PERFECT !!; if not set this value will be FALSEautooff = false; 14699+ has native http functions, but you are forced to be logged into use them; this patch removes that restriction, set to false to disable it if you have any problems; if not set this value will be TRUExhttp = true; when tempbcast is set to TRUE the raw temp data from smc will be broadcast over UDP at temptime second; intervals on port tempport; if not set this value will be FALSEtempbcast = false; if not set this value will be 10temptime = 10; if not set this value will be 7030tempport = 7030; when set to TRUE all titles will have the insecure socket priveledge; if not set this value will be FALSEsockpatch = false; when set to TRUE dash launch will not erase launchdata before launching a quick launch item; if not set this value will be FALSEpasslaunch = false; when set to TRUE various functions will be spoofed to make firmware think it's connected to LIVE; this does not compensate for the fact that it cannot contact LIVE servers; setting this to TRUE forces liveblock to TRUE; if not set this value will be FALSEfakelive = false; when set to TRUE network/cloud storage options should not show up in disk dialogs; if not set this value will be TRUEnonetstore = true; when set to TRUE a snapshot of the console temperature data will be displayed in the console shutdown dialog (displayed when guide button is held); !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S SHUTDOWN DIALOG MAY NOT BE PERFECT !!; enabling this option disables autooff; if not set this value will be FALSEshuttemps = false; when true, any devkit profiles on the console will not appear as corrupt and can be used; any changes such as saving games or getting achievements will resign the profile with the current/retail keyvault; this seems not to affect glitch/jtag dev crossflash, but could affect these profiles on true devkits; if not set this value will be FALSEdevprof = false; when true, system link data will be encrypted for communication with devkits; if not set this value will be FALSEdevlink = false; when true dash launch will perform automatic disk swapping; WARNING!! do not enable if you use FSD or swap.xex for this !!; if not set this value will be FALSEautoswap = false; when true, disables kinect health pseudo video at game launch; if not set this value will be TRUEnohealth = true; when true, disables dash locale setup screens when settings already exist; if not set this value will be TRUEnooobe = true; when true dash launch will automatically enable fakelive functionality only during official dash and indie play sessions; if not set this value will be FALSEautofake = false
  14. The splintercell issue is beyond the scope of dash launch. As far as I know, xbox is not capable of mounting a container inside of a GOD, you have to manually remove and install the Content folder from the one disk for it to all work right. Not sure if it would work if tried it extracted or not, but I know if you put the Content folder on the hdd along with normal Content folder on the hdd, and rebuild the iso without it in, GOD to GOD disk switching works fine.
  15. Unfortunately, these kinds of problems also occasionally happen on stock/unhacked machines. I'm sure the RMA centers have had to reflash quite a few machines that have bricked during an update or even just randomly, though in the case of an internal memory unit going corrupt usually the console works well enough that CSR would just tell you to format it again. Isn't it great that we can just back this stuff up ourselves whenever we want, rather than rely on RMA and send the console across the country to only get some other already refurbished console back in it's place losing the data anyway? :)I wonder too, if this is not the reason why they implemented cloud storage for gamesaves, though of course that also requires you pay them a subscription fee (LIVE) and have internet everywhere you use your machine.