xboxhacks.de - Deutsches Xbox 360 und One Forum für News, Hacks & Co.

Zitat

XeLLous v1.0 By Redline99
2010-01-22

Features (compared to mainline Xell):
New network stack, lwip 1.3.0
Uses correct MAC address if proper config blocks are in place
Sets DHCP "hostname" for easy identification in DHCP assignments
Refactored/New ata/atapi/mmc drivers
Updated sfcx driver with hardware detection
Many misc text changes/cleanups
Many misc code tweaks/fixes
Many new http features
Download Full raw nand backup
Download Decrypted Key Vault (if available)
Download Fuses (and DVD Key if available) as a text file
Download RAW Key Vault (equivalent to nandpro -r switch)
Download RAW Config Blocks (equivalent to nandpro -r switch)
Prominent display of CPU and DVD keys
Ability to set dvd key from Key Vault to DVD Drive
(possible use: fix bad key flashes to the original drive)
Advanced Nand Flashing
Uses "slot" technique from usb as introduced by Flash360
Write Flash partition from usb (up to 66 MB)
Write Flash partition from optical media
Write FULL raw nand (up to 528 MB) from optical media

USB (FAT-FAT32):
Place in the root dir of the media.

updslot0.bin - Xell (Address 0x0C0000 max length 0x040000 bytes, no metadata)
updslot1.bin - Rebooter (Address 0x100000 max length 0x140000 bytes, no metadata)
updpatch.bin - Rebooter Patches (Address 0x194000 max length 0x004000 bytes, no metadata)

updflash.bin - Nand Image File (this must include the metadata or aka spare/ecc bytes)
This can be up to 66 MB maximum, this covers the Flash Partition on even 256/512 MB
consoles.

CD-ROM / DVD:
Place in the root dir of the media.

updflash.bin - Nand Image File (this must include the metadata or aka spare/ecc bytes)
Must be the full nand with exceptions for consoles with a built in Memory Unit.
For consoles with built in MU you can write just Flash partition (66 MB) to the nand.

USB Notes:
For best results of getting the usb device detected. Remove the power plug from the console
after running the MS dashboard. Then reinsert the power plus, insert usb device and then
boot into XeLLous.

Reading 66MB (updflash.bin) can take a few minutes, be patient while it loads to ram.

Flash Notes:
updflash.bin must include the key vault and config blocks if you require them. XeLLous
WILL OVERWRITE what is on the nand with what is contained in the updflash.bin

Bad Block handling will be invoked if:
Ran from usb
Only data in the Flash Partition
Is one of the following: updslot0.bin, updslot1.bin, updpatch.bin
Is a updflash.bin AND NO PRE-REMAPPED blocks are detected in the file.

Http Notes:
The HTTPD is very primitive, we are not running Apache or anything so be kind to it
and don't open more than one connection.

In testing FireFox has been determined to have the best user experience. Internet Explorer
does work, but seems to have trouble initiating downloads. Once the download has began
IE seems to work ok.

The "Set DVD Key" should only be used by people who fully understand its use. This
is not a DVD flashing feature and it doesn't fully pair a dvd to the Key Vault. It
simply reads the dvd key from the Key Vault and instructs the dvd drive to store
that key in its firmware. It doesn't not in return store the dvd's OSIG in the
Key Vault and it does not Flash the DVD firmware. You probably don't have a use for it.

TFTP Notes:
Currently hardcoded to "192.168.1.98/tftpboot/xenon"

Order of Operations: (first condition meet excludes all the rest)
USB Media
updslot0.bin
updslot1.bin
updpatch.bin
updflash.bin
xenon.elf

Optical Media
updflash.bin
vmlinux

Network Init
DHCP: Auto Assigned (hostname "XeLLous")
Static: 192.168.1.99

Network TFTP
192.168.1.98/tftpboot/xenon

Network HTTPD
Waits on port 80 of displayed IP Address

Files: (Another set of the same for Cygnos compatibility)
The main difference here is the loading address, various versions have been built
and used at different times for different setups, I've inclused all that I know of.

Rename one of these files to "updslot0.bin"

File Name: Loading Address: Example use:
xell-1f.bin 0x1c000000 original jtag hack, xbr_1, xbr_2
xell-2f.bin 0x1c040000 xbr_3, freeboot .1, freeboot .2
xell-readcd.bin 0x01310000 King Kong exploit
xell-serial.bin 0x01300000 King Kong exploit
xell-xell.bin 0x02310000 Not A Clue.




Future ?? Who knows when, maybe never, feedback needed/wanted ??:
Faster nand speeds, ie: I can triple download speeds from http
Downloading Encrypted KV and Config Blocks
More Flashing features/bad block handling
More HTTP features/tools
Sata HDD Driver
Full CPU Speed
File System driver layer fat/fatx/iso9960/etc ?
Read some sort of XeLLous.ini file for parameters
Such as: Network config, Order of operations, etc...


Thanks:
To all the gracious people who helped test! These are the ones I can remember:
Cr4zi3, Skorchir, Ocelot13, SpkLeader, Zoneout

Greets:
r0wdy, tiros, MODFREAKz, schtrom, xorloser, tmbinc, seventhson, angerwound, kreet, lantus,
Skorchir, D-BlooD, momdad, skitzo, Cr4zi3, Sonic-Iso, stk50, Yoshihiro, Arakon and Alley.

Team Greets:
XBRebooter, XeDev, Jungle, HyperX, Avalaunch, Xecuter,
MS Interactive Entertainment Business Department