› Foros › Xbox 360 › Exploits y homebrew
tinete escribió:FranScorpions escribió:Pues sí. Pero te faltaría instalar los avatares también para que te funcionen todos los juegos, eso es muy fácil y está explicado por varios sitios.
Y a parte instalarle el dashlaunch 2.27 o tambien va incluido en todo el proceso??????
liachuvigo escribió:recomiendo a la gente que use su nand modificada.yo fui listo y cuando envie una de mis consolas a la tienda,peticione que me dieran la nand y la nand modificada.esa use,usando el autogg 0.2.1 .
consola: jasper 16 megas(ignoro si small o big)
prueba con nand "pre-rgh" = pantallazo negro,luz verde encendida.ni se activaban los ventiladores,pero el shell entraba como siempre..aunque me cambio de color negro a color azul.
prueba con nand "ggibuild" = funcional 100%
por cierto,en dashlaunch tengo lo de nonupdate en true y pongo la carpeta renombrada a $$SystemUpdate pero no me la autodetecta para el tema de los avatares...que hacer?
serxiu escribió:albur escribió:serxiu escribió:si en el paso 11 para saber la placa pone solo jasper¿cual de las 4 q hay es?(266mb 512mb jasper 16mb jasper 16bm sb)
GRACIAS
Yo he sacado la nand y me ha dicho la placa que tenía, jasper, y los 16Mb cuando he hecho la copia de la nand he visto que tenía 16Mb, como no ponía nada más le he dado a esa, la de 16Mb sb no sé que és.
Que alguien te confirme si hay otra manera.
GRACIAS YA HE DESCUBIERRTO COMO SE HACE HE ENTRADO EN NADFLASH.BIN.LOG Y ALLI PONIA PLACA:JASPER SIZE:16MB
alexisr11 escribió:Este tutorial sirve para que tipo de consola....
me explico...
- Sirve para una con RGH o JTAG 13604?
- Si es asi solo basta con seguir estos pasos? o hay q actualizarla primero al 14699 Oficial y luego aplicar los pasos?
Gracias por la respuesta. Atte. Alexis
Messiahs escribió:alexisr11 escribió:Este tutorial sirve para que tipo de consola....
me explico...
- Sirve para una con RGH o JTAG 13604?
- Si es asi solo basta con seguir estos pasos? o hay q actualizarla primero al 14699 Oficial y luego aplicar los pasos?
Gracias por la respuesta. Atte. Alexis
Sirve para ambas simplemente, selecciona lo que tienes en el punto 1.
alexisr11 escribió:
Oks, gracias por la respuesta.
¿Que me recomiendas conveniente actualizar oficial a 14699 y después seguir los pasos?. Tengo una slim con RGH chip Matrix dash 13.604
Atte. Alexis
Messiahs escribió:alexisr11 escribió:
Oks, gracias por la respuesta.
¿Que me recomiendas conveniente actualizar oficial a 14699 y después seguir los pasos?. Tengo una slim con RGH chip Matrix dash 13.604
Atte. Alexis
Hazlo tal como lo tienes, por que si actualizas a la oficial, luego como flasheas?
GUILLERMO01 escribió:Dejando de lado el tema de kinect, (en el dash anterior funciona no?) en algun momento se hará necesario instalar el dash 14699 o el dashlaunch 2.27 para jugar a lo que esta por venir ? o podemos quedarnos en el 13699 y 2.26 de por vida?
acabo de dejar la consola apuntito y con lo que me ha costado, no quiero asumir un riesgo extra si no me aporta una ventaja respecto a lo que tengo ahora, (o si se hace necesario)
muchas gracias a los dos por el tuto.
bye.
Messiahs escribió:GUILLERMO01 escribió:Dejando de lado el tema de kinect, (en el dash anterior funciona no?) en algun momento se hará necesario instalar el dash 14699 o el dashlaunch 2.27 para jugar a lo que esta por venir ? o podemos quedarnos en el 13699 y 2.26 de por vida?
acabo de dejar la consola apuntito y con lo que me ha costado, no quiero asumir un riesgo extra si no me aporta una ventaja respecto a lo que tengo ahora, (o si se hace necesario)
muchas gracias a los dos por el tuto.
bye.
Imposible de saber a ciencia cierta, pero lo normal es que si en algún momento tendrás que actualizar, normalmente con el Jtag no hacen falta los updates menores. Pero este al cambiar el Dash y eso puede que si sea necesario en un futuro. Pero vamos puedes esperarte hasta que sea imprescindible y listo. Ahora mismo no hace falta para nada.
GUILLERMO01 escribió:Dejando de lado el tema de kinect, (en el dash anterior funciona no?) en algun momento se hará necesario instalar el dash 14699 o el dashlaunch 2.27 para jugar a lo que esta por venir ? o podemos quedarnos en el 13699 y 2.26 de por vida?
acabo de dejar la consola apuntito y con lo que me ha costado, no quiero asumir un riesgo extra si no me aporta una ventaja respecto a lo que tengo ahora, (o si se hace necesario)
muchas gracias a los dos por el tuto.
bye.
kayser666 escribió:GUILLERMO01 escribió:Dejando de lado el tema de kinect, (en el dash anterior funciona no?) en algun momento se hará necesario instalar el dash 14699 o el dashlaunch 2.27 para jugar a lo que esta por venir ? o podemos quedarnos en el 13699 y 2.26 de por vida?
acabo de dejar la consola apuntito y con lo que me ha costado, no quiero asumir un riesgo extra si no me aporta una ventaja respecto a lo que tengo ahora, (o si se hace necesario)
muchas gracias a los dos por el tuto.
bye.
Ahora que leo al compañero he caido en la pregunta... si actualizo el dash (el del RGH claro) actualizare "el oficial"? o solo el dash del RGH? perdere el flaseo? o no pasa nada?
Gracias.
Messiahs escribió:kayser666 escribió:GUILLERMO01 escribió:Dejando de lado el tema de kinect, (en el dash anterior funciona no?) en algun momento se hará necesario instalar el dash 14699 o el dashlaunch 2.27 para jugar a lo que esta por venir ? o podemos quedarnos en el 13699 y 2.26 de por vida?
acabo de dejar la consola apuntito y con lo que me ha costado, no quiero asumir un riesgo extra si no me aporta una ventaja respecto a lo que tengo ahora, (o si se hace necesario)
muchas gracias a los dos por el tuto.
bye.
Ahora que leo al compañero he caido en la pregunta... si actualizo el dash (el del RGH claro) actualizare "el oficial"? o solo el dash del RGH? perdere el flaseo? o no pasa nada?
Gracias.
El Dash del RGH es el Oficial. Lo que no tienes que hacer es actualizar con el Update Oficial de microsoft, por que para meter la imagen modificada de nuevo habría que soldar.
Por eso se crea con el xeBuild y se flashea con un programa homebrew, asi mantienes el Hack y actualizas el Dash.
kayser666 escribió:Ok el perfecto hasta ahi..¿pero y el flaseo?(me refiero por supuesto al FW de C4eva el L.T.2.0)
Messiahs escribió:kayser666 escribió:Ok el perfecto hasta ahi..¿pero y el flaseo?(me refiero por supuesto al FW de C4eva el L.T.2.0)
Esto es para flashear la consola, no el lector. Son cosas totalmente diferentes
kayser666 escribió:Messiahs escribió:kayser666 escribió:Ok el perfecto hasta ahi..¿pero y el flaseo?(me refiero por supuesto al FW de C4eva el L.T.2.0)
Esto es para flashear la consola, no el lector. Son cosas totalmente diferentes
Si hombre ya lose, pero no me he debido de expresar con claridad...
Se que esto es para el RGH, eso esta todo OK mi pregunta es: si actualizo el dash (en forma de RGH) el flaseo del lector se pierde?(como de costumbre al acutalizar el dash original) perdona si estoy pez o no me explico pero llevo con el RGH poco más de 1 mes...
kayser666 escribió:Ok el perfecto hasta ahi..¿pero y el flaseo?(me refiero por supuesto al FW de C4eva el L.T.2.0)
Esto es para flashear la consola, no el lector. Son cosas totalmente diferentes
Si hombre ya lose, pero no me he debido de expresar con claridad...
Se que esto es para el RGH, eso esta todo OK mi pregunta es: si actualizo el dash (en forma de RGH) el flaseo del lector se pierde?(como de costumbre al acutalizar el dash original) perdona si estoy pez o no me explico pero llevo con el RGH poco más de 1 mes...
No, el flash se pería por que microsoft necesito actualizar los lectores para que pudieran leer el nuevo formato XGD3, ni si quiera con la actualización oficial se pierde el flasheo con esta versión.
Y creando la Nand hackeada, en ningún caso se pierde, el lector se queda tal y como esta. Como te he dicho son cosas totalmente diferentes, y con este tutorial solo tocamos lo referente a la consola.
por Africa 09 Dic 2011 18:18
Sin embargo, no me gusta nada este nuevo dash. Supongo que para los "oficiales" conectados online y tal quedará chulo y practico, pero para los que tenemos hack offline.... Máxime cuando no posees kinect.
gosty escribió:por Africa 09 Dic 2011 18:18
Sin embargo, no me gusta nada este nuevo dash. Supongo que para los "oficiales" conectados online y tal quedará chulo y practico, pero para los que tenemos hack offline.... Máxime cuando no posees kinect.
Pues yo también he actualizado mi jasper de 512 mb, y todo perfecto. Y en cuanto a la forma de este nuevo dash, es feo de cojones. Y es feo tanto online, como offline, ya que en mi slim conectada online, he visto un poco el goltv, y los menus, y me parecen feos de narices.
un saludo.
pombito escribió:Perdon pero soy mu novato, como encuentro la cpukey, he arrancado el xellmenu y no so dnd encontrarla, si me podeis decir los pasos a seguir o algun tutorial
shinodajx escribió:Buenas a todos, siguiendo el tuto, al crear mi nueva nand, el log me dice "fcrt.bin not found, skipping",¿que significa eso?, porque si que la crea, y pone todo ok al final, creo que hay otro compañero al que le pasa igual que a mi. Gracias de antemano.
FranScorpions escribió:gosty escribió:por Africa 09 Dic 2011 18:18
Sin embargo, no me gusta nada este nuevo dash. Supongo que para los "oficiales" conectados online y tal quedará chulo y practico, pero para los que tenemos hack offline.... Máxime cuando no posees kinect.
Pues yo también he actualizado mi jasper de 512 mb, y todo perfecto. Y en cuanto a la forma de este nuevo dash, es feo de cojones. Y es feo tanto online, como offline, ya que en mi slim conectada online, he visto un poco el goltv, y los menus, y me parecen feos de narices.
un saludo.
Cuestión de gustos, porque a mí me molan más así que antes. Y lo del kinect y el reconocimiento de voz es un puntazo.
gosty escribió:por Africa 09 Dic 2011 18:18
Sin embargo, no me gusta nada este nuevo dash. Supongo que para los "oficiales" conectados online y tal quedará chulo y practico, pero para los que tenemos hack offline.... Máxime cuando no posees kinect.
Pues yo también he actualizado mi jasper de 512 mb, y todo perfecto. Y en cuanto a la forma de este nuevo dash, es feo de cojones. Y es feo tanto online, como offline, ya que en mi slim conectada online, he visto un poco el goltv, y los menus, y me parecen feos de narices.
un saludo.
Africa escribió:FranScorpions escribió:gosty escribió:
Pues yo también he actualizado mi jasper de 512 mb, y todo perfecto. Y en cuanto a la forma de este nuevo dash, es feo de cojones. Y es feo tanto online, como offline, ya que en mi slim conectada online, he visto un poco el goltv, y los menus, y me parecen feos de narices.
un saludo.
Cuestión de gustos, porque a mí me molan más así que antes. Y lo del kinect y el reconocimiento de voz es un puntazo.
¿Y como haces para mostrar el listado de juegos xbox360?
Saludos.
sergi333 escribió:vamos a ver si me aclaro con esto , voy a actualizar mi slim con rgh pero antes quisiera saber si puedo hacer una copia de la nand que tiene actualmente por si pasa algo durante la actualizacion poder volver la consola a su estado antes de actualizar ¿eso lo puedo hacer? a ver si me ayudais ,como se hace la copia , con que programas , como se restaura , si es posible sin tener que soldar , gracias
xeBuild GUI 1.0
0
Swizzy's xeBuild GUI Version 1.0
---------------------------------
****** If you find a bug, let me know! you can reach me on: admin@swizzy.se ******
****** NOTE: I did NOT create xeBuild! i merely made a frontend/gui for it! ******
======================================================================
Requirements - What you need to do have in order for this to work!
======================================================================
- Microsoft .NET Framework 3.5 or later
- Your CPUKey
- A dump of your nand
======================================================================
Overview - What it does
======================================================================
- This is a frontend/GUI for xeBuild, what it does is make it easy
for you to select most options that you might need, such as Motherboard,
SMC hack for freeboot, image type etc. etc.
- It is able to check what SMC hack you have previously used for JTAG
it's also able to tell you what SMC version you have, and if it's a
JTAG, Clean/Retail, Glitch or Cygnos patched SMC
- If you put any of these files next to the executable it'll use them
automaticly:
SMC.bin - Custom SMC of your choice; ONLY USE THIS OF YOU KNOW WHAT
YOU ARE DOING!!!!
Xell.bin - Custom Xell of your choice; ONLY USE THIS OF YOU KNOW WHAT
YOU ARE DOING!!!!
cpukey.txt - It'll read the first line of this file as CPUKey
flashdmp.bin - It'll load this as source nand
Default.xml - It'll load any preset settings from this file
options.ini - It'll load any custom settings from this (for xeBuild)
launch.ini - Settings for Dashlaunch, if you choose to use this setting
it'll include this file in the built image
======================================================================
Notes about building retail images
======================================================================
Retail images can be built using this gui, it includes common retail
SMC's i've extracted myself, i make no form of garantuee that these
are safe to use for your console, some machines might not like the
bootloaders etc. which are used by default...
======================================================================
Notes about LDV
======================================================================
There are 3 ways you can get your LDV value:
1. Use Xell and manually count the ammount of "f" on fusesets
07 and 08, the total here is your LDV value.
2. Use Xell and a network connection, doing this the app can
read fusesets for you and read cpukey aswell as check what ldv your
Xbox 360 should have automaticly for you (this option also sets both)
3. Use 360 Flash Dump Tool and check which value is the highest, this
is the one you will want to be using
Normally (if you have a good dump that does NOT include data from
.ECC file created using RGH python script) xeBuild should be able
to extract this value on it's own, if it can't just follow the
instructions above... if you don't understand these instructions,
ask google!
======================================================================
Notes about FCRT patches
======================================================================
This patch removes the need for FCRT.bin in nand, however, it will
NOT work for everyone, it's been enabled in the default configuration,
but should be disabled if you are using a machine with a Liteon DG16-D5S
FW: 1175, it's been confirmed by me that it doesn't work on these drives
all others i've tested has worked just fine, however it can still be a
problem for you to have this activated, disable it if games don't work
from discs (if you use this feature!)
======================================================================
Changelog - New features and bug fixes
======================================================================
**************
* KNOWN BUGS *
**************
- Whiles checking SMC the app may sometimes crash if using a bad dumped
image, or an image with badblocks in it...
*******
* 1.0 *
*******
- Initial release
- Dashlaunch 2.27 is the version included with this release
- xeBuild 1.0_Hot Fix is the version used with this release
- This version supports building the following Dashboard versions:
- 2.0.7371.0 - Retail images ONLY
- 2.0.9199.0 - JTAG images ONLY
- 2.0.12611.0 - JTAG images ONLY
- 2.0.12625.0 - JTAG images ONLY
- 2.0.13146.0 - JTAG images ONLY
- 2.0.13599.0 - JTAG, Retail and Glitch images
- 2.0.13604.0 - JTAG, Retail and Glitch images
- 2.0.14699.0 - JTAG, Retail and Glitch images
* Files for 2.0.14699.0 are included *
======================================================================
Credits - Thanks to:
======================================================================
- cOz - Maker of Dashlaunch, been talking ALOT to him asking for advice
- Razkar - Helping me find bugs and giving me general advice/ideas, along with
releasing this app on logic-sunrise!
- Jack Nepacha - Making my new icons, thanks mate
- Anyone else that has helped me with anything such as tests, bug finding
and such that is not mentioned above, THANK YOU! without testers this app
would be pretty much useless compared to the other GUI versions out there
****
at time of this writing, this is ONLY compatible with:
"freeBOOT": 9199, 12611, 12625, 13146, 13599, 13604, 14699
"ggBuild" : 13599, 13604, 14699
read info_launch.ini for info on options and setting launch parameters.
****
================================================================================
important note about the new keyswitcher
================================================================================
Retail encrypted xex that are not validly signed will not load due
to the way the new keyswitcher works.
================================================================================
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, and the controller must
sync to the top left quadrant (player 1.)
- 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 - see 1.0 release for a windows patch builder
- 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 freeboot version installed on the console
- get the installer to a place where you can run it, and do so. Follow onscreen
instructions. The installer will prompt you if it needs to update the
freeboot patches and will give you an opportunity to configure the new
options
- edit and place launch.ini where you would like it, see note below as well
**See inlcuded sample and the info ini which describes the options allowed**
note: the installer includes upgrade paths for dash launch 1.0 users, it will
optionally update launch.ini files wherever found to use the new path names
================================================================================
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
****
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.
================================================================================
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 or system settings
================================================================================
INI notes
================================================================================
-it's possible to have multiple ini files, priority is: USB, HDD, BB MU, FLASH
(** 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.
-see http://code.jellycan.com/simpleini/ for more info on the ini parser
-if you find your ini file is not working, open it in a hex editor and ensure
that windows didn't convert it to a non-ASCII format by putting identifyer
bytes at the beginning of the file. The first charater in a hex editor
should be whatever the first character you have in the ini file, not
non-character codes like 0xFF or similar
================================================================================
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.
================================================================================
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 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 fbbuild, keeping us on our toes and up to date!
-Thanks to xbox-scene for always putting up a release thread announce!
-Greetz to XeDev
-shouts out to E Nellie and D33per, this a sourceless release!
~brought to you by cOz~
07/12/2011
================================================================================
Known Bugs
================================================================================
- Thanks to excellent testers, none were corned by the time of this writing. If
you find any during use, find the release thread at xbox-scene and please
report them there.
- in freestyle 1.7 and earlier, there was a minor glitch that caused console
crashing for some people under rare circumstances, if you haven't updated
to RC1.8 or newer please do so.
- corrupt games when launched return to NXE to display the corrupt game UI
Enlaces relacionados:
Novedades de la versión 2.27 (Ver lista de cambios completa)
- removed FCRT patch (was not compatible with 1175 drives)
- installer: revise patch checks to only check base patches
- installer: conform to xebuild's base+patch extension method, copies addon patches to
base as needed
- add 14699
learsy28f escribió:Muchas gracias por el tuto, genial
Yo quiero dejar mi aportación, mirrors del software necesario y su información original:
http://q.gs/927111/****rxeBuild GUI 1.0
0
Swizzy's xeBuild GUI Version 1.0
---------------------------------
****** If you find a bug, let me know! you can reach me on: admin@swizzy.se ******
****** NOTE: I did NOT create xeBuild! i merely made a frontend/gui for it! ******
======================================================================
Requirements - What you need to do have in order for this to work!
======================================================================
- Microsoft .NET Framework 3.5 or later
- Your CPUKey
- A dump of your nand
======================================================================
Overview - What it does
======================================================================
- This is a frontend/GUI for xeBuild, what it does is make it easy
for you to select most options that you might need, such as Motherboard,
SMC hack for freeboot, image type etc. etc.
- It is able to check what SMC hack you have previously used for JTAG
it's also able to tell you what SMC version you have, and if it's a
JTAG, Clean/Retail, Glitch or Cygnos patched SMC
- If you put any of these files next to the executable it'll use them
automaticly:
SMC.bin - Custom SMC of your choice; ONLY USE THIS OF YOU KNOW WHAT
YOU ARE DOING!!!!
Xell.bin - Custom Xell of your choice; ONLY USE THIS OF YOU KNOW WHAT
YOU ARE DOING!!!!
cpukey.txt - It'll read the first line of this file as CPUKey
flashdmp.bin - It'll load this as source nand
Default.xml - It'll load any preset settings from this file
options.ini - It'll load any custom settings from this (for xeBuild)
launch.ini - Settings for Dashlaunch, if you choose to use this setting
it'll include this file in the built image
======================================================================
Notes about building retail images
======================================================================
Retail images can be built using this gui, it includes common retail
SMC's i've extracted myself, i make no form of garantuee that these
are safe to use for your console, some machines might not like the
bootloaders etc. which are used by default...
======================================================================
Notes about LDV
======================================================================
There are 3 ways you can get your LDV value:
1. Use Xell and manually count the ammount of "f" on fusesets
07 and 08, the total here is your LDV value.
2. Use Xell and a network connection, doing this the app can
read fusesets for you and read cpukey aswell as check what ldv your
Xbox 360 should have automaticly for you (this option also sets both)
3. Use 360 Flash Dump Tool and check which value is the highest, this
is the one you will want to be using
Normally (if you have a good dump that does NOT include data from
.ECC file created using RGH python script) xeBuild should be able
to extract this value on it's own, if it can't just follow the
instructions above... if you don't understand these instructions,
ask google!
======================================================================
Notes about FCRT patches
======================================================================
This patch removes the need for FCRT.bin in nand, however, it will
NOT work for everyone, it's been enabled in the default configuration,
but should be disabled if you are using a machine with a Liteon DG16-D5S
FW: 1175, it's been confirmed by me that it doesn't work on these drives
all others i've tested has worked just fine, however it can still be a
problem for you to have this activated, disable it if games don't work
from discs (if you use this feature!)
======================================================================
Changelog - New features and bug fixes
======================================================================
**************
* KNOWN BUGS *
**************
- Whiles checking SMC the app may sometimes crash if using a bad dumped
image, or an image with badblocks in it...
*******
* 1.0 *
*******
- Initial release
- Dashlaunch 2.27 is the version included with this release
- xeBuild 1.0_Hot Fix is the version used with this release
- This version supports building the following Dashboard versions:
- 2.0.7371.0 - Retail images ONLY
- 2.0.9199.0 - JTAG images ONLY
- 2.0.12611.0 - JTAG images ONLY
- 2.0.12625.0 - JTAG images ONLY
- 2.0.13146.0 - JTAG images ONLY
- 2.0.13599.0 - JTAG, Retail and Glitch images
- 2.0.13604.0 - JTAG, Retail and Glitch images
- 2.0.14699.0 - JTAG, Retail and Glitch images
* Files for 2.0.14699.0 are included *
======================================================================
Credits - Thanks to:
======================================================================
- cOz - Maker of Dashlaunch, been talking ALOT to him asking for advice
- Razkar - Helping me find bugs and giving me general advice/ideas, along with
releasing this app on logic-sunrise!
- Jack Nepacha - Making my new icons, thanks mate
- Anyone else that has helped me with anything such as tests, bug finding
and such that is not mentioned above, THANK YOU! without testers this app
would be pretty much useless compared to the other GUI versions out there
======================================================================
======================================================================
http://q.gs/927111/dash-launch-v227zip
Dash Launch 2.27
----------------
****
at time of this writing, this is ONLY compatible with:
"freeBOOT": 9199, 12611, 12625, 13146, 13599, 13604, 14699
"ggBuild" : 13599, 13604, 14699
read info_launch.ini for info on options and setting launch parameters.
****
================================================================================
important note about the new keyswitcher
================================================================================
Retail encrypted xex that are not validly signed will not load due
to the way the new keyswitcher works.
================================================================================
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, and the controller must
sync to the top left quadrant (player 1.)
- 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 - see 1.0 release for a windows patch builder
- 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 freeboot version installed on the console
- get the installer to a place where you can run it, and do so. Follow onscreen
instructions. The installer will prompt you if it needs to update the
freeboot patches and will give you an opportunity to configure the new
options
- edit and place launch.ini where you would like it, see note below as well
**See inlcuded sample and the info ini which describes the options allowed**
note: the installer includes upgrade paths for dash launch 1.0 users, it will
optionally update launch.ini files wherever found to use the new path names
================================================================================
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
****
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.
================================================================================
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 or system settings
================================================================================
INI notes
================================================================================
-it's possible to have multiple ini files, priority is: USB, HDD, BB MU, FLASH
(** 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.
-see http://code.jellycan.com/simpleini/ for more info on the ini parser
-if you find your ini file is not working, open it in a hex editor and ensure
that windows didn't convert it to a non-ASCII format by putting identifyer
bytes at the beginning of the file. The first charater in a hex editor
should be whatever the first character you have in the ini file, not
non-character codes like 0xFF or similar
================================================================================
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.
================================================================================
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 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 fbbuild, keeping us on our toes and up to date!
-Thanks to xbox-scene for always putting up a release thread announce!
-Greetz to XeDev
-shouts out to E Nellie and D33per, this a sourceless release!
~brought to you by cOz~
07/12/2011
================================================================================
Known Bugs
================================================================================
- Thanks to excellent testers, none were corned by the time of this writing. If
you find any during use, find the release thread at xbox-scene and please
report them there.
- in freestyle 1.7 and earlier, there was a minor glitch that caused console
crashing for some people under rare circumstances, if you haven't updated
to RC1.8 or newer please do so.
- corrupt games when launched return to NXE to display the corrupt game UI
Enlaces relacionados:
Novedades de la versión 2.27 (Ver lista de cambios completa)
- removed FCRT patch (was not compatible with 1175 drives)
- installer: revise patch checks to only check base patches
- installer: conform to xebuild's base+patch extension method, copies addon patches to
base as needed
- add 14699
tinete escribió:Los avatares no me salen,,y he hecho lo que dice en el manual renombrandolo a $$ystemupdate ,,osea ,,lo meto en el pendrive y en el dash original no me hace nada.
Por cierto y antes de que se me olvide MUCHAS GRACIAS A FranScorpions y a todos los que me habeis ayudado.Decir que ya tengo instalado el nuevo dash,,pero ahora:
-No se me descargan las caratulas
-no tiene inicio rapido y siempre que salgo de un juego me lleva al dash principal
-No me sale lo del avatar
Africa escribió:
¿Y como haces para mostrar el listado de juegos xbox360?
Saludos.
tinete escribió:Los avatares no me salen,,y he hecho lo que dice en el manual renombrandolo a $$ystemupdate ,,osea ,,lo meto en el pendrive y en el dash original no me hace nada.
Por cierto y antes de que se me olvide MUCHAS GRACIAS A FranScorpions y a todos los que me habeis ayudado.Decir que ya tengo instalado el nuevo dash,,pero ahora:
-No se me descargan las caratulas
-no tiene inicio rapido y siempre que salgo de un juego me lleva al dash principal
-No me sale lo del avatar.Como hay que renombrar el systemupdate con los $$ y una vez metido en la consola debe saltar solo el pendrive o que hay que hacer????
Gracias compañeros
XRain escribió:tinete escribió:Los avatares no me salen,,y he hecho lo que dice en el manual renombrandolo a $$ystemupdate ,,osea ,,lo meto en el pendrive y en el dash original no me hace nada.
Por cierto y antes de que se me olvide MUCHAS GRACIAS A FranScorpions y a todos los que me habeis ayudado.Decir que ya tengo instalado el nuevo dash,,pero ahora:
-No se me descargan las caratulas
-no tiene inicio rapido y siempre que salgo de un juego me lleva al dash principal
-No me sale lo del avatar.Como hay que renombrar el systemupdate con los $$ y una vez metido en la consola debe saltar solo el pendrive o que hay que hacer????
Gracias compañeros
Me pasa lo mismo, no hay forma que me coja el update. Ni poniendo $ ni $$. No lo coge.
Lo de las caratulas ni lo he probado.
SAludos.