Jump to content
OGXbox.com

KaosEngineer

Moderators
  • Posts

    4,879
  • Joined

  • Last visited

  • Days Won

    460

Posts posted by KaosEngineer

  1. 3 minutes ago, Steven Mrozek said:

    Thanks for this, I do have a few questions though.

    So it should go down like this:
    Install modchip
    Flash the M7 Bios to the chip
    Follow those directions?

    Also, where is A15 point on a 1.0 motherboard? And it says connect D0 to ground, does that mean don't connect it to the modchip?

    Yes.  Both D0 and A15 are manually moved from ground to disconnected at the appropriate time during the recovery process.  I need to find the picture with A15's location shown.  I'll post it here soon.

  2. X3 BIOS is specifically made for the X3 modchip.

    DO NOT FLASH THIS BIOS TO THE XBOX TSOP OR ANY OTHER NON-X3 MODCHIP!

    There are ways to restore the flash by connecting, IIRC, 3 additional wires to the motherboard and jumper them to GND at the appropriate time to regain access to the TSOP after booting from a modchip with a special recovery BIOS - read this thread at assembergames.com (AG).

    Or, the new XBlast Lite modchip by bennydiamond @ AG (a.k.a. psyko_chewbaccacan be used to fix a bad TSOP flash.  The older Chameleon modchip could be used for TSOP flash recovery too.

    Or, unsolder the TSOP EEPROM from the motherboard and use a FLASH programmer (eBay search for TL866CS or TL866A with a 40-pin TSOP adapter) to reprogram it with a compatible properly sized BIOS then reinstall it.  (Install a 40-pin TSOP socket similar to what Andrew "bunnie" Huang did when he worked on hacking the Xbox after it was first released.

    "bunnie" is the author of the book: Hacking the Xbox available in the downloads section here at ogXbox.com or from the publisher's website for FREE!)

    Excerpt from bunnie's open letter about why he decided to release the free PDF of his book (prefer a physical copy, the softcover edition is still available for purchase online):

    Quote

    Dear Reader,

    No Starch Press and I have decided to release this free ebook version of Hacking the Xbox in honor of Aaron Swartz. As you read this book, I hope that you’ll be reminded of how important freedom is to the hacking community and that you’ll be inclined to support the causes that Aaron believed in. ...

    • Like 1
  3. 7 hours ago, wikati said:

    i can also vouch for the chip working, you are limited to 256k bios but ind5003 does work rather nicely.

    But not on a v1.6, M8plus_16.bin required for it.

  4. 7 hours ago, VeeBee Goon said:

    I'm have a 500GB Seagate Barracuda. I just used XBpartitioner 1.3 to reformat F and G and made one big F partition. I used the 32KB cluster size available. 

    After doing so, run XBPartitioner v1.3 again to verify that the correct cluster size took hold. 

    Sometimes the process doesn't work the first time around and defaults to the wrong cluster size.  Therefore, always verify that the correct cluster size, no "ER" displayed, after a reboot and running XBP v1.3 a second time.

  5. opps!  If much data was copied from the disk it overwrote part of what was already there corrupting files. 

    The "ER" is the indication that the wrong cluster size is configured for that partition.  The drive should be reformatted in the Xbox. (ALL DATA WILL BE LOST! However, it already is.) Use XBPartitioner v1.3 to format the extended partitions to set up the correct cluster size.

    Extended partition cluster sizes:

    64KB clusters for up to max of 1TB partition
    32KB clusters for up to max of 512GB partition
    16KB clusters for up to max of 256GB partition

    What size is the partition in question?  Did you have F and G?  What size is the HDD?

  6. On 2/15/2018 at 4:24 PM, ShawnS said:

    In the default dashboard it says K: 1.00.4977.01 and D: 1.00.5960.00. In evoxdash it says bios unknown and kernel 1.00.4977.01 if I go into the Flash BIOS menu it looks like I have X2_4977 available. That might be the last installed BIOS? 

    2

    Yeah, the BIOS needs to be updated. I'm not sure 4977 has LBA48 support if not the max HDD size is 137GB 

    The lastest 256KB X2 BIOS is 4983 and 512KB X2 BIOS is 5035.  There are also a few more compatible BIOS's that could be used on your modchip and console - EvoX M8plus, iND-BiOS 5003 or the Beta iND-BiOS Feb-11-05 (aka 5004) = all 256KB in size.

    I'd download a copy of HeXEn 2017 installer disc, extract and burn a copy to DVD-R. Boot the disc. It does take a minute before the menu appears so wait for it. Next, select the menu option to flash a BIOS to your modchip/TSOP.

     

  7. If you start the stock MS dashboard go into System Info scroller at the end it shows the kernel - K: 1.00.KKKK.01 and dashboard - D: 1.00.DDDD.01 .  What value is KKKK and DDDD as it's there too?

    Or, UnleashX shows the Kernel version in the System Info page - from the main menu press Y and look for it: 1.0.KKKK.1. Press B to return to the main menu.

    Evoxdash with the appropriate skin selected will display the BIOS and Kernel versions too.

  8. I see the same thing 3.8.0 latest official release to support XP, others have said 3.9.0.1 or .2 worked for them on XP SP3 Pro.

    Older versions are available at sourceforge.net.  You have to click on "Browse all files" to browse the listings to locate them.

    edit: Wow, sourceforge did a major site upgrade. Click on the Files tab to browse the project's files.

    https://sourceforge.net/projects/filezilla/files/FileZilla_Client/3.8.0/

     

  9. On 1/23/2018 at 6:32 PM, wikati said:

    Yes, Xecuter 2 BIOS Manager (X2BM v2.3) is used to flash this X2 modchip connected to a Windows PC's ECP/EPP parallel printer port. (Win9x / 2k / XP work not sure if it will run on anything newer.)

    --edit--

    Doesn't start correctly on windows 10.  Must enable compatibility mode Windows XP (Service Pack 3) for error-free startup.  However, as my FFC cable to connect external programmer board to modchip is messed up, I cannot verify that it can actually program my X2Pro modchip.

    --end--

    X2 BIOS Manager (X2BM v23).JPG

    • Like 1
  10. Check the underneath side of the motherboard for trace corrosion along the front edge.  These thin easily damaged traces carry processed power and eject button closure status to the PIC processor (System Management Controller - SMC).

    O52PATG.jpg

    Typical trace corrosion on the back (solder side) of the ogXbox motherboard - grid section 7V.

    Follow the P/E board Troubleshooting steps found at the link previously supplied - http://diy.sickmods.net/Tutorials/Xbox1/Power-Eject_Pinouts/

    • Like 1
  11. XBMC doesn't show the X, Y and Z partitions and creates the Q as a virtual drive/path substitution to the location of the folder that contains XBMC's default.xbe file be it C:\XBMC4Xbox\, E:\<blah>\<blah>\, F:\myxbmc\, G:\XBMC\ etc. This subfolder's location is mapped to Q:\ for a consistent access path to XBMC's files and folders.

    From Using XBMC - XBMC4Xbox.org.uk:

    What is the Q drive?

    The Q drive is a path substitution to your XBMC installation folder. So if for instance XBMC is installed in E:\Apps\xbmc, the Q drive points there.

    And from XBMC4Xbox's FAQ Troubleshooting section: 

    Why can't I access X, Y or Z partition using eg. My Files or by FTP?

    Early on a decision was made to make it a little 'harder' for new unknowing users to access X, Y or Z due to the fact that these are "cache partitions" and no data put there stays there. You can make them a source yourself in Filemanager or edit Filezilla Server.xml and add these.

  12. There are two separate apps.  One app that edits both of these BIOSes config files does not exist.

    The iND-BiOS config app comes with the archive for the 5003 BIOS release or separately as iND-BiOS Config App v.0.4.30

    An X2 Config Maker's nfo file states, "x2 Config Maker for 'x2 5032 ONLY'": not sure that's correct is latest on xbins ftp server. You'd think it would work with 5035 too but not per the docs or a typo:

    The X2Config.rar that chipntschip provided a link to works for 5035.  Doesn't look infected to me from scans by MalWareBytes or Windows Defender.

    The x2config.ini can be edited with a text editor same goes for the ind-bios.cfg file.

    These apps do give visible color previews and show all the options available which are handy.

    • Like 2

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.