Jump to content
OGXbox.com

Search the Community

Showing results for tags 'kernel'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Rules
    • Why Can't I Download?
  • Subscribed Members Only
    • Subscribed Members Only
  • Off Topic
    • New Member Introductions
    • Rumble Pit
    • Suggestion Box.
  • General Xbox Discussion
    • General Xbox Discussion
  • Original Xbox Modding Forum
    • Hardware Mods
    • Modchips
    • TSOP Flashing
    • Softmods
    • Repair
  • Xbox Case Modding
    • Case Mods
    • Lighting & Electrical Mods
  • Tutorials
    • Official Tutorials
    • Tutorial Submission
  • Software
    • Bios
    • Dashboards
    • Installation Disks
    • Applications
    • Games
    • Emulators
    • Homebrew
  • Xbox Collecting
    • Xbox Collection Showcase
  • Rare and Uncommon
    • Rare and Uncommon Xbox Hardware
    • Rare and Uncommon Xbox Software
  • Vendors
    • N64 Freak's Products
    • Barnito's Products
  • Development
    • Rocky5's Projects
  • Online Play
    • Game Night
  • Classifieds
    • Wanted
    • For Sale
  • Moderator Section
    • Moderator Back Room

Product Groups

  • Vendor Forum
  • Membership Subscriptions
  • Forum Ads

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 11 results

  1. https://github.com/gaasedelen/titan#overview Overview Titan is a series of hand-written binary patches for the original Microsoft Xbox kernel. These patches are designed to expand the storage capabilities of the popular 2001 game console in excess of 16TB. This is achieved by modifying the kernel to support LBA48 and extending the number of addressable 512-byte disk sectors in the IO stack. Special thanks to Mike Davis for his serial debugging boards, Matt Borgerson for his tireless efforts on XEMU & FATX, and finally Paul Bartholomew (oz_paulb) for his original LBA48 research from 2003 which facilitated up to 2TB for the past 15+ years. All of these people and their open-source works played an important role in the creation of Titan. Disclaimer This project does NOT use any copyrighted code, or help circumvent security mechanisms of an Xbox console. These patches should be considered highly experimental pending further attestation. By using this software, you accept the risk of experiencing total loss or destruction of data on the console in question. Titan may break existing Xbox homebrew, and existing homebrew may break Titan-based systems. Usage Titan's PC-based kernel patcher is written in Python 3. It is strongly recommended that you download the released packages which bundle the applicable dependencies for Windows, Linux, and macOS. Example usage is provided below: python3 tpatch.py m8plus_kernel.img Successful output should look something like the following: [*] Patching with Titan v1.0 -- by Markus Gaasedelen [*] - Hashing kernel 'C:\titan\m8plus_kernel.img' to ensure compatibility [*] - 0x800243AA: Patching HddStartVerify(...) [*] - 0x8002443F: Patching HddVerify(...) [*] - 0x800244E6: Patching HddStartRw_Length(...) [*] - 0x80024534: Patching HddStartRw_Transfer(...) [*] - 0x80024632: Patching HddRw_Save(...) [*] - 0x8002465B: Patching HddRw_Smuggle(...) [*] - 0x80024485: Patching HddCompleteRw(...) [*] - 0x800246F3: Patching HddGetDriveGeometry(...) [*] - 0x8002F066: Patching HddPartitionCreate(...) [*] - 0x80024B5A: Patching HddCreateQuick(...) [*] - 0x8005546D: Patching HddCreate(...) [*] - 0x80027143: Patching FatxParseSupeblock(...) [*] - 0x80029CE5: Patching FatxStartAsyncIo(...) [*] - 0x80029E5B: Patching FatxAsyncIo(...) [+] Patching successful! For a full walkthrough of setting up an Xbox with Titan, please refer to the GUIDE.md provided in this repo. Additional Notes Some additional notes about Titan are as follows: Formatting The FATX project is currently the only tested/supported method to format a disk for a Titan-based system XBPartitioner/XBlast/XeniumOS/FATXplorer are all considered unsupported and probably require updates I fully expect these tools to get updated releases in the near-future Partitions Titan is essentially hardcoded to use a 'F (Partition 6) Takes All'-esque partitioning scheme Titan could be extended to support additional partitions, but it seems unnecessary Clusters Titan allows increased cluster sizes of 128kb, 256kb and 512kb It is strongly recommended to format large disks (2TB+) with 1024 sectors per cluster (512kb) Matt's FATX is the only tool that can currently format disks with larger clusters Increased cluster sizes dramatically increases the speed of mounting FATX volumes (faster bootup) Increased cluster sizes will ensure more linear reads on the disk (faster file reads, game loading, etc.) Increased cluster sizes allows for more items in the root disk directory (8192 items at 512kb clusters) If you're using Titan, you can afford the luxury of bigger clusters so stop complaining about wasted space Increased cluster sizes were never the issue for limiting drive/partition sizes, this is FUD 64kb clusters should work on the Titan partition but bootup/mounting WILL be slow for large disks UDMA Titan can change the UDMA transfer mode used by the kernel with --udma N Increasing the UDMA mode has been profiled to improve some game load times in excess of 20% Increasing the UDMA mode will require an 80pin IDE cable The retail Xbox uses UDMA 2 (33mb/s) by default (as do many/all (?) modified BIOS') The maximum supported UDMA mode by the Xbox southbridge is UDMA 5 (100mb/s HDD <--> CPU) UDMA 5 DOES NOT WORK WITH ALL IDE TO SATA ADAPTERS UDMA 5 has been confirmed working with Startech adapters but has not been properly benchmarked UDMA 5 is unstable on RXD-629A7-7 based adapters, but UDMA 4 seems okay WLXKG-863B are the 'worst' adapters I have experienced working on Titan and are largely untested Games A random assortment of games have been tested to ensure some baseline on system stability I don't expect major issues here, but more testing should be obviously be done Dashboards XBMC seems to work fine EvoX seems to work fine EvoX displays the incorrect disk size because it performs a modulus of 'available gigabytes' by 1000 This does not mean that you formatted incorrectly, or that the HDD is corrupt FTP seems okay? Dashboard-based FTPs are probably much safer than BIOS-based FTP (eg. XeniumOS) Consider all other dashboards as untested Other Homebrew Notes DVD2Xbox works fine FTP via XeniumOS is probably risky. I would only use it to transfer files onto RETAIL partitions (C or E) Anything booting into a BFM BIOS (PBL, Hexen?) is totally unsupported for accessing the Titan partition (F) Consider all other homebrew as untested Patches Titan is only supported on the M8+ kernel. M8+ is a modified version of the final retail kernel (5838) Titan/M8+ can be used on ALL retail hardware revisions (1.0 -> 1.6b) These patches can almost certainly be ported to other Xbox kernels, but not something I plan on doing Previous iterations of these patches modified the kernel to use 4K sectors but was deemed unnecessary The released patches can be further simplified, moving away from the original 4K implementation More experimental patches that further accelerate mounting large FATX volumes may be added later
  2. What ups So glad I found this awesome forum for the OG. I installed an OpenXenium chip and now I don't know what to do. My goal is to swap the original HDD (which is EVOX softmodded) with a spare 1TB I have laying around. I tried adding the retail kernel to the launch menu but it isn't working. On the original HDD the xbox boots to a black screen, on the spare HDD the xbox boots to an error screen. What is my next step?
  3. A bit late to the party as it's been floating around for ages.. The past few months I have been tinkering with the Xbox tree seeing how it works.. and much like my work with the NT 5 tree, Environment Variables will totally change a build. I'm making this thread to list down what environment variables I know (most will already know this), as a reference for me and anyone interested.. Also citation on errors or misinformation is greatly welcomed, I won't be putting the standard "_NT386TREE" kind of ones.. Anything with a * I am unsure about.. These are related to targeting "Retail" and trigger quite a few changes during build. • RETAILXM3=1 • OFFICIAL_BUILD=1 * or • RETAILXM3P=1 • OFFICIAL_BUILD=1 * This one caused a load of errors, I didnt look much into this one yet. • COVERAGE_BUILD=1 * For some reason this one was never set for the tree I work with, some postbuild scripts require this. • _BUILDVER=4400 This one seems to affect more 'closer to production' build options, several postbuild scripts rely on this set. • COMPUTERNAME=XBuilds This one needs to be set before razzle gets to "ntuser.cmd" as it specifies build options. • NTDEBUG=release Causes: • 'ltcg ~dm' to be added to %BUILD_OPTIONS% • sets NTDEBUG=ntsdnodbg • sets NODEVKIT=1 But setting to: • NTDEBUG=free Causes: • 'ltcg profile' to be added to %BUILD_OPTIONS% • NODEVKIT=1 These are related to Checked builds. • BUILD_ALT_DIR=d • CHECKED_ALT_DIR= * • FREEBUILD=0 * This one is presumably set on retail builds • FREEBUILD=0 * This one in theory enables some alternative textures and model placements for the dashboard, most likely used during testing. • COOL_DASH=1 * This one I am unsure about its purpose, it's referenced throughout the code.. • SILVER= I will add more as I find them, if anyone else knows any worth noting please add!
  4. I grabbed a Kernel file from this page and I flashed it with XBlastOS. Does the kernel have to match the original kernel? What is the kernel relative to the BIOS? Normally kernel and BIOS are two very different components of a computer. I shouldn't have been able to flash the TSOP with the kernel correct? How are those kernels meant to be used? I was looking for the default BIOS. Thanks
  5. *Disclaimer: No links to file will be provided, this is for discussion only* Not sure if anyone has yet, but I have been running a diff between Barnabus Kernel Repack and the 4400 leak Kernel Tree.. I've only just started looking through, and I have next to no C++, C and C# coding skills so bear with me lol They seem somewhat the same, but there are quite a few files with parts of code removed or added, on both branches. But Barnabus is reliant on precompiled objects (obviously as it's a smaller, almost stripped down and made 'easy' release of the full tree) There are some comments in Barnabus code that isn't in the full tree + CPXXUPD code, and some are recorded more 'formally' (i.e private\ntos\init\init.c line 244 - 254 in both branches) One other thing is the 4400 tree is set to have 'complex's' edits definable where possible, which there are a lot.. One thing that really interests me, is Barnabus uses BIOSPack to pack: 2bl, remainder and kernel into a 'Working' rom (I use that word loosely). The 4400 tree uses rombld, which requires: preloaded, init table, bootloader, kernel and a rom decode file(I think).. this is a drastic difference to BIOSPack.. But the main issue with Rombld is it will not produce a full rom.. by default it will error on the 'preloader' being to big (9008 bytes not 1664 bytes).. To get around that, we can either build for XDK Systems.. Or as I discovered today: modify 'private\sdktools\rombld\rombld.cpp' Line 879 from (2 * 1024) to (21 * 512), to allow rombld to accept the 9kb preloader file.. (I haven't tested a bios rom built with this edit yet) I will post here anything else I discover!
  6. This might interest those that want to turn their retail/debug Xbox into a fully-functioning development kit without having to spend $500+ on one. It works on any version 1.0 through 1.2 motherboard and can be great for troubleshooting crashes of all kinds without requiring the use of XDK software. I'm selling pre-made units for $30 plus shipping and would also like to get a feel for how many might want one in Europe so I can bulk-ship to a distributor to help save some on shipping costs as it's usually around $15 USD to ship from the US otherwise. Everything is fully open-source if you'd like to build/sell them yourself as well. Any questions, feel free to ask. https://github.com/XboxDev/serial-usb-adapter
  7. Does anybody know what kernels were used in various "hacked" bioses...? Eg. X2 4981 or iND-BiOS 5003 Looking at this page: https://xboxdevwiki.net/Hardware_Revisions 4981 or 5003 were... not released? Have the teams behind X2 and iND used their own versioning schemes or did they use some sort of development/beta/debug bioses...? Anyway - perhaps somebody knows what kernels the X2 4981 and iND 5003 use?
  8. Hello, I am looking at making a few of these for myself, and I'm wondering if anybody here has used one, or anything similar to it? I'm not familiar with kernel debugging using Super I/O, but it seems like something that could be useful if I want to learn all I can from the hardware of this system. DobaMuffin
  9. I have a Xbox (v1..1), Currently it has Modded with Spider Chip with M8+ Bios flashed. (* Its HDD content actually is softmoded, but due to old HDD failing, I cloned the content to the current HDD which is not lockable, thus had to use the spiderchip again) One of disadvantage of modchip is it doesn't support playing game from ISO directly, But nkpatcher seems only for softmod. Therefore, I searched and managed to find out from the post http://www.emuxtras.net/forum/viewtopic.php?f=187&t=3228&start=20, about using the amazing console app "cdrom_modchip" to load the ISO file. It works greatly without needing to config or code anything., except having to run/load the patcher every time after the xbox restart. Does anyone have any idea how to load the patcher.xbe automatically when the DASH started. From the post above, it was mentioned about configing the IND_Bios.cfg ( the order of DASH1, DASH2, DASH3 etc). But I don't like ind_bios, as I feel M8 bios is much clean and faster. . Thanks in advance Peter
  10. I have a Xbox (v1..1), Currently it has Modded with Spider Chip with M8+ Bios installed. (* Its HDD content actually is softmoded, but due to old HDD failing, I cloned the content to the current HDD which is not lockable, thus had to use the spiderchip again) One of disadvantage of modchip is it doesn't support playing game from ISO directly, But nkpatcher seems only for softmod. Therefore, I searched and managed to find out from the post http://www.emuxtras.net/forum/viewtopic.php?f=187&t=3228&start=20, about using the amazing console app "cdrom_modchip" to load the ISO file. It works greatly without needing to config or code anything., except having to run/load the patcher every time after the xbox restart. Does anyone have any idea how to load the patcher.xbe automatically when the DASH started. From the post above, it was mentioned about configing the IND_Bios.cfg ( the order of DASH1, DASH2, DASH3 etc). But I don't like ind_bios, as I feel M8 bios is much clean and faster. . Thanks in advance Peter
  11. Version 3.2500.1 CodeAsm REDACTED (Mail, pm or chat for more info) Tweeter twit CodeAsm_ 5-5-2015 [Incomplete version list Xbox, These are not the versions you are looking for.] [Some note removed or altered for internet storage savety. ] ???? XDK Alpha I SDK xxxxx ???? Alpha II Feb 2001, while mfc is 4/4/01 Mfc: 4/4/01 xxxxxxxxxxxxxxxxxxxxxx ???? XDK May 2000 xxxxxxx 3113 3146.2 Leaked (REC?)ISO 1-11-2000 November XDK 3146.3 ALPHA December 2000 XDK 15-12-2000 December XDK (also 16-12) ISO is 11.2 MB (11,810,816 bytes)xxxxxx xxxxx note*) 3223.1 ISO is 13.3 MB (14,024,704 bytes)xxxxxx 3224 February 2001 XDK and SDK , REC own 3306 3308 3331.1 March 2001 XDK and SDK xxxxxxxRecovery (nice side way dash) (7-03-2001 April XDK) 3332.1 LeakLeak video 01, REC, old style dash 3424.1 April 2001 XDK and SDK (03.01.01 - New for April XDK release) 3507 3514 3521.1 <<< Microsoft Xbox XDK (1.0.3521.1) (2001-05) > May 2001 XDK and SDK symbols 3604 3618 3633.1 Alpha SDK SYM (June 01) 3722 3813 3821 3823.1 Oldest for DVT3 (fixing an DVT3 on xxxxxxxxx) Oldest acording to xxxxxx for DVT3 3845\ 3907 3911 August XDK 2001 (( Final Hardware Recovery) (build on WIN2000 5. 2134/2195 ? 5.1.2258.400) xxxxxxxxxxxxxxxxxxxt 2001 final x08-46850 ----------------------------------------------------------------- Retail? ------------------------------------------------------------------- 3925.1 Retail? XDK xxxxxx 3944 < 4000 4023 4024 4028 4033 4034.1 (internet source KERNEL MCPX is X3 httxxxxxxxxxxxxxxxxd=50 (dash may be higher...) 4039 < 4119 4120 4121 4125 4134.? < 4134.6 01/29/2002 December 2001 XDK with Intergrated Hotfixes Release Histoxxxxx 4134.7 03/19/2002 December 2001 XDK with Intergrated Hotfixes Release History '' 4224 < 4228 4229 4234 4235 4242 01/19/2002 February 2002 XDK 4242.2 03/15/2002 February 2002 XDK with Intergrated Hotfixes '' 4300 4344 4346 4348 4354 4361 02/28/2002 March 2002 XDK Accession SDK ownSDK (Accession) 4361.2 03/15/2002 March 2002 XDK with Intergrated Hotfixes 4400 (xxxxxx source ?) Barnabas XDK, SDK 4432 03/29/2002 April 2002 XDK 4504.1 2002 Live Beta (kernel and dash) internet source (MCPX-X2 code asswell) 4531 04/28/2002 May 2002 XDK 4604.1 2002 Live beta consolexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: N 4627.1 06/05/2002 June 2002 XDK June WAM SDK 4721 06/26/2002 Juli 2002 XDK 4817 Kernel only? source interwebs, MCPX is X3 htxxxxxxxxxxxxxxx=50 4818 4831 07/31/2002 August 2002 XDK 4831.5 08/23/2002 August 2002 XDK with Intergrated Hotfixes 4831.6 08/29/2002 August 2002 XDK with Intergrated Hotfixes 4831.8 09/12/2002 August 2002 XDK with Intergrated Hotfixes 4831.9 10/18/2002 August 2002 XDK with Intergrated Hotfixes 4928 08/28/2002 September 2002 XDK parts 4928.2 09/12/2002 September 2002 XDK with Intergrated Hotfixes 4928.3 10/03/2002 September 2002 XDK with Intergrated Hotfixes parts 4928.4 10/18/2002 September 2002 XDK with Intergrated Hotfixes 4928.7 03/18/2003 September 2002 XDK with Intergrated Hotfixes recovery 5028 10/04/2002 October 2002 XDK 5028.3 10/18/2002 October 2002 XDK with Intergrated Hotfixes 5028.4 03/18/2003 October 2002 XDK with Intergrated Hotfixes iso? 5101 < Internet source 5120.1 10/31/2002 November 2002 XDK (parts andxxxxxxxx?) 5120.3 03/18/2003 November 2002 XDK with Intergrated Hotfixes 5120.4 04/09/2003 November 2002 XDK with Intergrated Hotfixes 5209 ARCDDASH, Segaboot (other libs are: 5028) 5233.1 12/12/2002 December 2002 XDK 5233.3 02/17/2003 December 2002 XDK with Intergrated Hotfixes 5233.4 03/18/2003 December 2002 XDK with Intergrated Hotfixes 5233.5 04/09/2003 December 2002 XDK with Intergrated Hotfixes 5344.1 02/04/2003 February 2003 XDK 5344.2 02/17/2003 February 2003 XDK with Intergrated Hotfixes 5344.3 03/18/2003 February 2003 XDK with Intergrated Hotfixes 5344.4 04/09/2003 February 2003 XDK with Intergrated Hotfixes 5455.1 04/18/2003 April 2003 XDK with Intergrated Hotfixes XDK 5455.2 04/18/2003 April 2003 XDK with Intergrated Hotfixes 5530 < Internet source 5558.1 05/30/2003 June 2003 XDK Recovery own 5558.2 06/20/2003 June 2003 XDK with Intergrated Hotfixes 5558.4 10/03/2003 June 2003 XDK with Intergrated Hotfixes 5659.1 07/30/2003 August 2003 XDK Recovery own, XDK also 5659.2 09/30/2003 August 2003 XDK with Intergrated Hotfixes 5659.3 (could be that this is the recovery? 5659.4 10/03/2003 August 2003 XDK with Intergrated Hotfixes 5659.5 11/20/2003 August 2003 XDK with Intergrated Hotfixes 5713 < Internet source 5788.1 11/11/2003 November 2003 XDK XDK Setup 5838 (kernel) < Internet source. 5849.0 recoveries [xxxx] 5849.1 and SDK REC 5849.6 (remote)recoveries [xxxxxxxxe] 5933.1 and SDK Remote recoverie [lxxxxxxxxve] (I own a version aswell) 5960.01 DAS (internet source txxxxxxxxxxxxxxxxx I got the 3146.3 iso from assemblergames, I noticed: A regular CDFS (not xbox) iso. DOS files (modded DOS 7.1 (win 98)) in the root A very NT-like boot sector. If you've seen those videos of early xbox alpha devkits, note the flash of 'Starting..' - that's io.sys. -------------------------------------------Xbox 360 ------------------------------------------------------- 2.0.nnnnn.n XX where xx is the newest board supported AlphaTower Xenon nov 2005 Zephyr may 2007 Falcon aug 2007 Opus july 2008 Jasper nov 2008 Jasper/Kronos mid 2009 Trinity/Velje may 2010 Corona aug 2011 SDK's: XDKSetupXenon6274.exe XDKSetupXenon8276.exe XDKSetupXenon11164.1 XDKSetupXenon11427 XDKSetupXenon11511 XDKSetupXenon11626 Recoveries: XDKRecoveryXenon111641Setup.exe XDKRecoveryXenon11164Setup.exe XDKRecoveryXenon11511Setup.exe XDKRecoveryXenon11775Setup.exe XDKRecoveryXenon120871Internal.exe XDKRecoveryXenon20353.exe XDKRecoveryXenon20764.10.exe XDKRecoveryXenon21076.6.exe Non remote recoveries: 1888_Xenon_Recovery.iso 4929_Xenon_Recovery.iso 5426_Xenon_Recovery.iso 7776_Xenon_Recovery.iso 7978_Xenon_Recovery.iso 8276_Xenon_Recovery.iso 9328_Xenon_Recovery.iso 9328.0_Xenon_Recovery.iso 9328.5_Xenon_Recovery.iso 9328.9_Xenon_Recovery.iso //2 versions: 1st) 483.700.736 bytes, MD5: 7C3E4F6620F76E19095623735F8180F0 2nd) 301.434.880 bytes, MD5: BDDF51AB55DE08FD223564BB0D0C49A4. first is hacked up and bricks your shit. 6995.1_Xenon_Recovery.iso 11164.1_Xenon_Recovery.iso 11164.3_Xenon_Recovery.iso 11775.3_Xenon_Recovery.iso 20353_Xenon_Recovery.iso 20871.2_Xenon_Recovery.iso //and 20871.2_Xenon_Recovery_with_Symbols.zip XDK's: XDKSetupXenon6274.exe XDKSetupXenon6534.exe XDKSetupXenon7645.1 XDKSetupXenon8276.exe XDKSetupXenon11164.3.exe XDKSetupXenon20871.2.exe XDKSetupXenon21076.11.exe XDKSetupXenon21119.0.exe //? need to verify other fanciful files: xdk-xna-extensions.msi //add XNA extensions to XDK, leaked from dev site XDK Kernel Version Flash Version Comment (Most are XeDK, other just version numbers) --------------------------------------------------------------------------------- 2.0.0198.0 2.0.????.0 First XDK Launcher Alpha 1 2.0.0417.0 ?????????? Giano code May (27) 2004 2.0.0418.0 ?????????? Giano code May (27) 2004 2.0.0422.0 ?????????? Giano code May (27) 2004 2.0.1232.0 2.0.????.0 Second XDK Launcher Alpha 2 2.0.1616.7 2.0.????.0 Seen on beta 007 kit. 2.0.1640.0 2.0.????.0 Seen on beta kit. 2.0.1746.1 2.0.????.0 Seen on a beta kit. First with keyvaults. 2.0.1800.0 2.0.????.0 ??? Nov 22, 2005 2.0.1810.5 2.0.????.0 XeDK 2.0.1838.0 2.0.1838.0 XeDK 2.0.1838.1 BETA 2.0.1838.1 Beta Launcher 2.0.1839.2 2.0.????.0 XeDK release Dashboard 2.0.1861.0 2.0.1861.0 XeDK (First w/ XEX2) 2.0.1888.0 2.0.1888.0 XeDK 2.0.2099.9 2.0.????.0 XeDK 2.0.2099.11 BETA 2.0.????.0 XeDK - Seen on a beta kit. 2.0.2135.0 2.0.????.0 XeDK 2.0.2255.0 2.0.????.0 ??? Jan 30, 2006 2.0.2417.0 2.0.2241.0 XeDK 2.0.2638.0 2.0.2258.0 XeDK 2.0.2638.0 2.0.2419.0 XeDK 2.0.2920.0 2.0.2832.0 XeDK - Remote includes 1888, 2241, 2255, 2258 and 2832 2.0.3215.0 2.0.2853.0 XeDK 2.0.3424.0 2.0.2858.0 XeDK 2.0.4314.0 2.0.4308.0 XeDK 2.0.4548.0 2.0.????.0 ??? 2.0.4802.0 2.0.????.0 XeDK 2.0.4929.0 2.0.4548.0 XeDK 2.0.5426.0 2.0.4548.0 XeDK - Last recovery KK exploit works 2.0.5632.0 2.0.4548.0 XeDK - Remote includes 4548 and 5632 2.0.5787.0 2.0.????.0 XeDK - ISO image in game format 2.0.6132.0 2.0.5759.0 XeDK 2.0.6274.0 2.0.5759.0 XeDK 2.0.6534.0 2.0.5759.0 XeDK - Remote includes 5787 (no 5759 ?) 2.0.6534.4 2.0.6683.0 XeDK 2.0.6707.0 2.0.????.0 XeDK 2.0.6995.0 2.0.6690.0 XeDK 2.0.6995.1 2.0.6690.0 XeDK 2.0.7645.0 2.0.6690.0 XeDK - Remote includes 6690 2.0.7645.1 2.0.6690.0 XeDK 2.0.7776.0 2.0.6719.0 XeDK 2.0.7776.1 2.0.6719.0 XeDK 2.0.7978.0 2.0.7342.0 XeDK - First on NXE 2.0.7978.3 2.0.7359.0 XeDK 2.0.8276.0 2.0.7366.0 XeDK 2.0.8953.0 2.0.????.0 XeDK 2.0.8955.0 2.0.????.0 ??? 2.0.8955.1 2.0.????.0 ??? 2.0.9177.0 2.0.9177.0 XeDK - Seen on beta XDK S, has a dumb flash number 2.0.9328.0 2.0.8464.0 XeDK - Remote includes 8464 and 7366 2.0.9328.5 2.0.8498.0 XeDK 2.0.9328.8 2.0.????.0 XeDK 2.0.9328.9 2.0.8955.0 XeDK - DO NOT RUN THE LEAKED ISO RECOVERY it was edited by TheFallen93 (afaik) and others to brick kits. You can find the real 9328.9 iso around though with filesize 301,434,880 bytes 2.0.11164.0 2.0.9189.0 XeDK 2.0.11164.1 2.0.9189.0 XeDK 2.0.11511.0 2.0.11025.0 XeDK 2.0.11626.0 2.0.?????.0 XeDK 2.0.11626.1 2.0.?????.0 XeDK 2.0.11763.0 2.0.12334.0 Rare Prototype Kinect Dashboard 2.0.11775.0 2.0.?????.0 XeDK 2.0.11775.3 2.0.12387.0 XeDK - ISO leaked from chinese forums, remote includes 12387 and 9199 2.0.11776.3 2.0.?????.0 XeDK 2.0.12087.1 2.0.?????.0 XeDK 2.0.12293.0 2.0.?????.0 XeDK 2.0.12387.0 2.0.?????.0 XeDK 2.0.15574.0 2.0.?????.0 ??? (ebay source) 2.0.16756.0 2.0.?????.0 ??? 2.0.17150.0 2.0.?????.0 ??? Dec 11, 2014 (wiki) 2.0.20353.0 2.0.12611.0 XeDK - Remote leaked from MS server 2.0.20353.2 2.0.12625.0 XeDK 2.0.20500.1 2.0.13139.0 XeDK 2.0.20764.10 2.0.13146.0 XeDK 2.0.21076.6 2.0.14699.0 XeDK 2.0.21119.0 2.0.14719.0 XeDK 2.0.21119.10 2.0.?????.0 XeDK 2.0.21173.8 2.0.15574.0 XeDK 2.0.21173.8 2.0.16154.0 XeDK 2.0.21250.2 2.0.16197.0 XeDK 2.0.21250.7 2.0.16202.0 XeDK RANDOM NOTES: 9328.9_Xenon_Recovery.iso //2 versions: 1st) 483.700.736 bytes, MD5: 7C3E4F6620F76E19095623735F8180F0 2nd) 301.434.880 bytes, MD5: BDDF51AB55DE08FD223564BB0D0C49A4. first is hacked up and bricks your shit. other fanciful files: xdk-xna-extensions.msi //adds XNA extensions to XDK, leaked from XDS how to remove digital signatures and help protect the guilty EXES (XDKSetupXenonxxxx.exe, XDKRecoveryXenonxxxx.exe) open EXE in hex editor and search for (in hex) A21E801C if more than one thing appears search for 5A30583033060A2B06010401823702010F3025030100A020A21E801C once you find that, either delete or null everything that comes after the 1C funny, this can also be used in reverse to identify the leakers, or tell if you have originals nvm this part: Xenon_Recovery, Xenon_Recovery.iso, _Xenon_Recovery, _Xenon_Recovery.iso, xxxx_Xenon_Recovery_with_Symbols.zip, _Xenon_Recovery_with_Symbols.zip, Xenon_Recovery_with_Symbols.zip, XDKSetupXenon, XDKSetupXenon.exe, XDKRecoveryXenon, XDKRecoveryXenon.exe, 11164.1_Xenon_Recovery.iso , 11164.3_Xenon_Recovery.iso, XDKRecoveryXenon20353.exe, 20353_Xenon_Recovery.iso, 1888_Xenon_Recovery.iso, 5426_Xenon_Recovery.iso, 4929_Xenon_Recovery.iso https://xds.xbox.com/xbox360/data/1033/xdksoftware/download/XDKSetupXenon9328.9.exe https://xds.xbox.com/xbox360/data/1033/xdksoftware/download/XDKSetupXenon11164.1.exe https://xds.xbox.com/xbox360/data/1033/xdksoftware/download/snorkel.exe ----------------------------------- Xbox one ------------------------------------------------------------- Giano (21 December 2010, kernel only) Durango ----------------------- ----------------------- Wordlist ----------------------- ---------------------- XDK Xbox Devolepment kit (xbox part) SDK Software Devolepment kit (PC) REC Recovery SYM Symbols KER Kernel DAS Dashboard FIL File (a loose file has been identified with this version LIB Library (part of xbe or software kit in wich diferences version.) DOC A documentation notion of official source NOT A unofficial notion of this version, still reverencing an MS source INC Incorrect number, probebly homebrew

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.