Slim Proto V2 In Production

We finally nailed the perfect glitch code for all slim consoles with the Slim Proto. We thank the many many members for their feedback and test results. Because of you we are now able to produce the perfect hardware that will work with all slims and require very little tuning (even less effort than the first slim proto)

Rather than come up with a fancy name i'll just stick with the brand name "proto" (which i guess is a fancy name in itself?) 

In production right now is the Slim Proto v2 – however this is the full version and not a prototype so don't be fooled by the name.

Changes:

  • Improved code – performance fine tuned
  • Smaller footprint/tighter circuit layout to give cleaner signal performance
  • Added ROL output support
  • Added CR_EN pad
  • No more solder bridges required
  • Includes custom made "pro" double shielded and grounded CPU_RST Cable
  • Supports Trinity & Corona v1 – v6

This product will replace the CR3 Pro which has now been discontinued. This will be the last Slim RGH device we will make, we feel that it just can't get any better.

For performance and test reviews of the Slim proto v1 please go here: http://team-xecuter.com/forums/forumdisplay.php?f=249

RRP $29.99 / £17.99 / €21.99 – of course we are also offering wholesale discounts and most retailers will pass those on to end users.

We have started accepting pre-orders from retailers so we suggest you contact your preferred retailer and ask them to get their orders in asap 

JungleFlasher v0.1.96 (Beta 323)

We have a brand new version of JungleFlasher for all you firmware fans JungleFlasher v0.1.96 (Beta 323) (Download is on XBINS) Changelog: We have a brand new version of JungleFlasher for all you firmware fans JungleFlasher v0.1.96 (Beta 323) (Download is on XBINS)

Changelog:

JungleFlasher 0.1.96(323)
========================================
support for Xecuter additional LTU2 files for DG-16D4S support
added extraction for DG-16D4S serial info from original drive at KeyCR time for LTU2 and LTU1

DashLaunch 3.09 Released

A new version of DashLaunch has been released with some minor bug fixes.

ChangeLog
================================================== ==============================
V3.09
- fix in update server for corona 16M consoles (thanks Danny Lane!)
- added exception logging to installer
- fix some minor bugs
- *known issue* 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. (thanks again Danny!)

V3.08
- tweak xelllaunch, see it's readme for how it's changed
- all patch sets updated to support xebuild update server full use
- added xebuild update server and related options
- fixed a bug with signnotice on 13604 (and probably older)
- changed farenheit to fahrenheit everywhere it wasn't before
- added 16537

Source: Xbins

C4E's LTU2 Firmware for all Liteon DG-16D4S !

C4E has listened to the many requests from users who have DG-16D4S drives and have no fw dump leaving them dead in the water. Until now.

From the nfo:

C4E's iXtreme LTU2 (DG-16D4S) in association with Team Jungle & Team Xecuter
—————————————————————————-

Official release of the iXtreme LTU2 for Team Xecuter LTU2 PCB (DG-16D4S)

As requested I have compiled the LTU2 firmware to now also work with Liteon DG-16D4S Drives

The Liteon LTU2 PCB will fit in both the D4S and D5S drive chassis of course.

- Support for all Liteon DG-16D4S 0225/0272/0401/1071

- No need for firmware dump of source drive. Requires dvdkey and J-Runner data

- Supports enhanced topology data if present for more accurate topology responses (Future ABGX support)

This firmware is uniquely written for the TX LTU2 board. Use the latest Jungle Flasher.

Thanks go to Team Xecuter & Team Jungle and all testers for their hard work and efforts in the development process.

Xbox One! Bring it on!

Thanks to everyone for the fun over the years! – C4E
SEPTEMBER 6TH 2013

LTU2-0225-v1.0.bin
MD5: 04F59E2843FDE513895986CE510E73A6

LTU2-0272-v1.0.bin
MD5: 4078859613FD83FD4EACCABBB421B91A

LTU2-0401-v1.0.bin
MD5: 2922147CDB267A4B9CEDC46FE08463B6

LTU2-1071-v1.0.bin
MD5: 2CB8CE453CA7A106A5EA2D433189944D

PS: I read some post by a Brazilian guy who claimed that you will be banned with LTU2. I wonder if it's the same
Brazilian guy who threatened to release this bullshit information if he didn't get a good deal on LTU2 boards?

In a butshell, don't listen to these idiots.

Xbox 360 Support to Last to 2016, Includes 100 New Games

Microsoft has announced that it will support the Xbox 360 for three more years before phasing it out in 2016.

Eurogamer reports that Xbox chief marketing and strategy officer Yusuf Mehdi explained at the Citi Global Technology Conference yesterday that the eight year-old console could expect to see over 100 new games before that time comes, however.

"You've seen us over the years constantly be focused on profitability and improving year over year," he said. "There are different points in the cycle of when you invest in new hardware.

If you look at 360 that platform lasted for seven to eight years and it's going to go for another three years. It's incredibly profitable now in the tail.

Some of these things take some time in the launch year in which you invest, and then they they play out over time."

Mehdi was adamant that the launch of the Xbox One wouldn't have a negative impact on the Xbox 360, insisting the two can and will co-exist happily until 2016 with over 100 new games coming to the older console.

"We're going to continue to invest in Xbox 360, and the two devices can work in concert," he said. "So it's not like the day we ship Xbox One your 360 won't work. We'll continue to support it."

If this comes to pass, it'll mean the Xbox 360 will have had an incredible 11 year life cycle, seeing as it launched in November 2005.

Source: IGN

Xbox One Confirmed Launch Date: November 22

The Xbox One launches in 13 markets including North America on November 22. After leaving it in the limbo of a November release window for a few months, Microsoft pinned a concrete release date on its next-gen system, one that'll see it arrive on North American retail shelves behind the PlayStation 4, due on November 15. On the other hand, the PS4 hits Europe one week after the Xbox One on November 29.

To recap, the Xbox One's 13 launch markets are:

  • Australia
  • Austria
  • Brazil
  • Canada
  • France
  • Germany
  • Ireland
  • Italy
  • Mexico
  • Spain
  • United Kingdom
  • United States
  • New Zealand

Meanwhile, Belgium, Denmark, Finland, the Netherlands, Norway, Russia, Sweden, and Switzerland, all initially on the launch list, won't see the Xbox One arrive until 2014.

As for the price, the Xbox One lands at $500 in the US, €500 in Europe, and £430 in the UK. The console's Standard edition includes the system, new Kinect sensor, Chat headset, and controller, as well as necessities including an HDMI cable, power supply, and Quick Start guide. Day One editions are also available at the same price, swapping out the Standard controller for a unique Day One controller with chrome d-pad, while also bundling in a Day One achievement code along with special packaging. In Europe, all Day One pre-orders score a free copy of football sim FIFA 14.

So that's it: We have dates and prices for both Sony and Microsoft's next-gen consoles, meaning we can finally plan the rest of our lives accordingly. Phew!

Source: joystiq

Mupen64-360 V0.993 Beta 2 (N64 Emulator)

A new version of the popular Nintendo 64 emulator for Xbox 360 has been released adding support for Corona and fixes USB issues.

New beta 2 of Mupen64-360 v0.993 emu for "hacked" Xbox 360. The main novelty here is the fix for some USB problems and Corona video support (Which was introduced in beta 1).

Here is the full changelog:

* Mupen64-360 v0.993 Beta2 *

http://www.libxenon.org/

Description

Mupen64-360 is a Nintendo64 emulator for the Xbox 360, it’s powered by libxenon and it’s a port of Wii64 (which itself was a port of Mupen64).

Usage

Unzip on USB sick, then run from Xell.

Many ROM formats are supported, zipped ROMs also work.

In the browser, the Back button changes the current drive, A selects, B goes to parent dir. Ingame, Back toggles Framerate limiting, and the Guide button quits to the browser.

Other controls are described in the emulator itself.

The browser background image is loaded from /mupen64-360/bg.png on the USB stick, other backgrounds are provided.

Options

  • Controls (l->r):
Changes the way N64 directional controls are mapped to the 360 gamepad, from left to right. EG: Stick / D-Pad / C-buttons means N64 stick will be mapped on the 360 left stick, N64 D-pad on 360 D-pad, and N64 C-buttons on 360 right D-pad.
  • Textures:
Changes the texture enhancement filter, depending on games, some filters will look better than others. Be aware than the highest settings can slowdown games a lot, or even crash them in some rare cases.
  • CPU core:
Controls the speed/compatibility ratio, from fully featured dynarec to interpreter mode. ‘No linking’ and ‘No VM’ are new dynarec modes that can make some games work, while still running at playable speed.
  • Framerate limiting:
When enabled, games won’t go faster than they would on a real N64. Can be toggled ingame with the Back button.

History

v0.993 BETA2:

  • Fixes mount issues with USB devices (which caused nothing to work) My Bad! //Swizzy

v0.993 BETA: Recompilation with some ZLX and Libxenon fixes

  • Supports Corona Video Output
  • Better USB Drive/HDD Compatibility

v0.992 Beta: Almost a complete rewrite, notable changes:

  • Moved to Mupen64 Plus core.
  • Moved to Rice video plugin.
  • Dynarec overhaul.
  • Faster and way more compatible.
  • More control over the speed/compatibility ratio (see ‘CPU core’ option)
  • More texture enhancement filters.
  • Basic controls remapping.
  • GUI improvements.
  • Built with recent libxenon/ZLX (more supported filesystems, less bugs, …)
  • /! Use the Guide button to quit a game, Back toggles framerate limiting now.

v0.96 Beta: First binary release

Credits

Wii64 / Mupen64 teams (guess why) :)
GliGli (Xbox 360 port)
Ced2911 (GUI library)
Razkar (Backgrounds)
Everyone that contributed to libxenon…

Sources: 360crunch.net

J-Runner Version v0.3 (Build 1) Released

Following the releases of the latest 360 dashboard 2.0.16537, Xell Reloaded 0.993Xebuild 1.08, and DashLaunch 3.08 J-Runner has update to include all of these including many under the hood fixes and new features

Version 0.3 Build 1

  • Support for new dashlaunch/xeBuild
  • Latest XeLL
  • Support for 16537 dash
  • XVal, why? no reason
  • XVal related function but for secdata.bin
  • Get Latest System Update function (hope MS won't bother JR downloading it)
  • xsvf LPT support for XP users (for those cheap asses who didn't buy a JR Programmer)
  • ECC files updated with new XeLL
  • both minor and major bugfixes and bug creations (As always please report bugs to make JR better)

Official Thread & Download

XeBuild 1.08 with new update feature

XeBuild 1.08

Introduction:
xeBuild is a command line system image builder for JTAG, glitch, and clean images.
Run the xeBuild program with no (or incorrect) args to see it's usage info.

What's New:

  • new boot chain and patches for trinity/corona that uses virtual efuses from CBB onward
  • added ability to fine tune content of the BL that glitching targets
  • new nolan addon patch for machines with bad wired LAN phy (boots to E75/76/77)
  • single addon provided to disable all internal memory units on arcade consoles
  • added client and update modes
  • 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 interal 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 reflashing 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.realmodsc…rum/15-xebuild/ (english)
http://homebrew-conn…x.php?board=8.0 (english/french)

Credits:
Without ikari this would not have been possible, thanks!

[v0.09 - 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 ******.

Don't believe what random people *cough* write on forums ..

Changes:
1.08

  • align patch slots properly on glitch images
  • add ability to make zero-paired dual cb images (retail/glitch)
  • unknown devkit smcs were not being checked properly and always reported hacked
  • added support for 'blmod.bin' per-build file, can assist fine tuning glitch machines that don't play well with standard patches
  • added CPU key corruption checks
  • added a secondary check on naddump.bin size after determining big block/small block
  • added new build target, glitch2m, which uses mfg cba to boot (currently only trinity/corona 16203 provided) with virtual fuses
  • added nolan addon patch for 16197+ for those with bad wired lan phy getting E75/76/77; should not affect wireless dongles
  • consolidate internal memory unit disable patches into nointmu addon, Corona 4G internal memory can now be disabled (16197+)
  • added integrity checks for: blocks that appear to be remapped but are outside the remap area; CF slot size
  • updated all patch sets to use hv built in memcpy (better peek support for things that require 64bit reads like 1bl ROM)
  • check for SU container in version\$SystemUpdate subfolder as well as version folder
  • nonces will attempt to be kept when providing NANDdump.bin (some claim this affects glitch boot times, makes differential flashing more effective)
  • Xstress.settings has been renamed to Manufacturing.data
  • update jtag freeboot core to V0.9 – use options stored in flash header instead of patched directly into the binary
  • added update and client mode
  • -d options no longer need to be relative to the exe launch path
  • checks keyvault signature (if present) when MAST_pub.bin is available from update server or file in .\ or .\common\
  • checks CB/CBA signature when 1BL_pub.bin is available from update server or file in .\ or .\common\
  • updated xell builds to XeLL_Reloaded-2stages-v0.993

http://www.youtube.com/watch?v=UL9rrDXfhCU

You can discuss this news on our forums as well as download here

Dashlaunch v3.08 Released

c0z has released an update for his must have xbox360 homebrew app DashLaunch. Version 3.08 brings support for the new dashboard and the amazing remote update feature for XeBuild.

From the Readme:

Dash Launch 3.08
—————-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 (1020×720) 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 0×4000 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\01 234567890123456789;
will have 01234567890123456789.data folder beside it
disk2 = Hdd:\Content\0000000000000000\01234567\00004000\98 765432109876543210;
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.realmodsc…/14-dashlaunch/
french/english: http://homebrew-conn…x.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
-shouts out to E Nellie and D33per, thanks to you this is still a sourceless release

~brought to you by cOz~
//2012

================================================== ==============================
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)
- 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
13599 is the first glitch version supported (embedded patches)
14717 is the first glitch2 version supported (embedded patches)

================================================== ==============================
ChangeLog
================================================== ==============================
V3.08
- tweak xelllaunch, see it's readme for how it's changed
- all patch sets updated to support xebuild update server full use
- added xebuild update server and related options
- fixed a bug with signnotice on 13604 (and probably older)
- added 16537

You can discuss this news on our forums as well as download here

« Previous Entries Next Entries »

Download mp3