Jump to content
OGXbox.com

Leaderboard

Popular Content

Showing content with the highest reputation since 06/29/2021 in all areas

  1. Intro Since the beginning of time (2004) it was known that the 1.6 was missing the unpopulated footprints for the extra 4 RAM chips and this made the upgrade impossible. I was thinking recently that if all the signals for the extra RAM chips are still available on the board, we can add RAM to the 1.6 by just connecting all the necessary signals. After the tutorial segment I'll go into why this mod works. I'll also post a video on YouTube at some point. Be warned: this is more difficult that a 1.0 - 1.5 RAM upgrade Tutorial Required items Everything mentioned in the 1.0 - 1.5 RAM upgrade tutorial: https://consolemods.org/wiki/Xbox:RAM_Upgrade 4x 90mm long mod-wire. I used enamelled wire from a transformer. ~8 hours spare time Step 1: flash the modified XBlast OS BIOS XBlast OS (as a BIOS) is super helpful in doing this install correctly. It will boot with any number of extra RAM chips and includes a test for the additional RAM. XBlast OS will not show the 128MB test option on a v1.6 Xbox, so I've gone ahead and rebuilt it from source with that check removed. xblast_os_custom_shows_128MB_test.bin If you don't trust my build, this is the line of code that needs removing: At this point, I suggest booting it up and running the test. The test is under Settings > Tools > 128MB RAM test Step 2: Remove the motherboard from the Xbox Step 3: Place the new RAM chip on top of an existing chip You'll want to solder down the corner pins first to get a good mechanical bond and so that you can adjust the alignment. I do this by pushing down pins 30 and 31 and soldering them down to the chip below. Then I check the alignment of the rest of the pins. If it's bad, then the chip can be nudged into position while reflowing the two pins. Then solder the two pins opposite. Step 4: Push down the rest of the pins Except pin 28! That is the chip select pin and it is unique for each RAM chip. Leave this pin floating in the air and don't solder it yet. Pin 30 is marked on the PCB. The pins come in a kind of ‾‾\__ shape. When you push them down, the whole pin will rotate around this end -> ‾‾\__ . I like to also push down the tail ‾‾\__ <- of the pin to get more contact with the chip below. Step 5: Start soldering all the pins Very little extra solder is required. Use lots of flux. I like the tacky flux that usually comes in syringes. I also like the drag-soldering method. If there's any excess solder, you will get shorts between pins and this extra solder can be wicked away. The new pins won't naturally touch the pins below even after pushing them down. Step 6: Check for shorts and missing connections For the first pass, I like to go in with a microscope and nudge each pin (of the new chip) with a cold soldering iron tip. If the pin moves easily, it is not soldered. Also check for shorts at the same time. If you have the patience (and want it to work first try without frying your Xbox), check for shorts and continuity with a multimeter. I skipped this the first time and got bitten! Best to clean the pins and pads with IPA before checking with the multimeter. Step 7: Add the chip-select wire First, figure out which bank you are adding: Then, find the chip-select solder point: Bank 1 CS is left of the label for C4P10 Bank 2 CS is between the labels for C4R12 and C4R13 Bank 3 CS is left and above the label for C4P21 Bank 4 CS is between and above the labels C4R1 and C3R1 For banks 2 and 3, the chip-select wire can go through the hole to the left of the GPU. For bank 2, 90mm may be too short, so check the wire length and cut it as short as possible. I removed the GPU heatsink to access this hole. At this point, it should look something like this: Step 8: Reassemble and test in XBlast For a quick test, I don't bother with adding the fan, GPU heatsink, HDD, or DVD drive. The test in XBlast should look like what I first posted on reddit: If the Xbox reboots twice and FRAGs, check the bios selection (if you have one available). A normal BIOS will not accept between 1 and 3 extra RAM chips. If the Xbox reboots three of four times (and it's faster than a normal FRAG sequence) check for shorts. This happened to me. Step 9: Repeat for the other 3 chips The first one is the hardest. Step 10: Reflash with your favourite BIOS Some 1.6 BIOSs won't support 128MB. The X3 BIOS works just fine and it's the only one I tested so far.
    13 points
  2. I try to stay in the background because the site is really about you all and I would never want to have much if any focus on me. With that said... I have always loved Xbox modding. I was really into it back in 2002-2004. I learned all I could and modded lots of Xboxs back then. I changed careers in 2014 and that took me to a new state and somehow all of that change rekindled my love for Xbox. I looked around for people who were still into it and they were scattered everywhere. Xbox-scene was dying/dead. I created the FB group and it took off relatively quickly. I did a lot of things wrong there by choosing the wrong admins and commenting on topics unrelated to Xbox.... moderating in a way that was frankly unprofessional. (I still do from time to time if I'm in a weird mood.) Once the FB group membership got around 10k, we started having content just disappear from the FB group. I became aware that the group could quite literally vanish in the blink of an eye. My skillset is in the world of IT, so spinning up a web server was really no trouble. So I fired up a VM on my server at home, set it up and allowed it through my firewall and announced the site. Once the site grew, I went ahead and moved it to a VPS cloud host so it doesn't depend on my home's power and internet reliability. Hopefully I covered whatever you were looking for. If not let me know and I'll answer almost anything.
    9 points
  3. >>> OGXBox 2021 XBlastOS 8MB MC TSOP Flasher <<< I finaly managed to get the (for me) perfect TSOP flasher done. It makes use of the known save game exploids for SC, MA, 007 & TH4 and uses XBlastOS to flash any TSOP right away. As base it will load up UnleashX where you can choose the bios you like to flash (See list below). After you have selected the bios UnleashX will unrar all necessary files and copy them to the needed places and after that XBlastOS will start. Also a pretty bare bone UnleashX will be installed in which you boot after the TSOP flash from which you can launch an installer like the OGXBox Installer 2021 to set up your HDD. So no more softmodding before TSOP'ing or using EvoX, Raincoat or Resctoox to flash a TSOP. All bios files and configs are pre-configured to boot up the evoxdash.xbe of the C drive. Here is a list of provided bioses: XBox v1.0 - 1.1 ONLY! - x2 5035.67 (512kb) XBox v1.0 - 1.3 ONLY ATM! - Cerbios v1.02 ALPHA (256kb) (Will be updated when newer version come out) XBox v1.0 - 1.4 - EvoX m8 plus noDVD (256kb)* - EvoX m8 plus yesDVD (256kb)* - iND 5003.67 (256kb) - iND 5003.67 XISO (256kb) - iND 5004.67 (256kb) - x2 4983.67 (256kb) And since this version is only 6.2MB in size (Incl. all save games!), you could add your own bios files beside the others. Screenshot : https://imgur.com/a/nBwAIIY Pre release version video (The final is slightly different but you get the idea) : https://www.youtube.com/watch?v=Zam2SXG1WI8 All credits go to these guys and teams: pysko_chewbacca, Rocky5, Team Cerbios, Team iND, Team Xecuter, Team EvoX and Team Unleash. Download sites (Pal and NTSC version): https://1fichier.com/dir/dyFJYcXu https://mega.nz/folder/cJ8XRAYZ#cCK8TgW1RsPWPkGvGSiUmA Have fun.
    7 points
  4. Oh no, another flasher! YES! I have resently read from the one or the other that it would be nice to have a option to just flash a bios wihtout the need to install any apps, dashboards or what ever. So I decided to make that DVD for the 2-3 ppl. out there. So this DVD provides XBlastOS and EvoX as flashing tool. Like the MC/USB installer I made, all bios files are already packed as bios.bin so you can flash any TSOP (Incl. Winbond) or ModChip with it right away. Other as the MC/USB flasher this DVD version provides more bios files you can flash. And ofc there is also a XBox 1.6/1.6b flasher on board. And no, if you didn't have already a modded XBox you need to use the MC/USB TSOP flasher (Or you soft mod). How ever. On the main screen you simply select what you like to do: Flash XBox 1.0-1.4 Without Dashboard Install. Flash XBox 1.0-1.4 With Dashboard Install. Flash XBox 1.6-1.6b Without Dashboard Install. Flash XBox 1.6-1.6b With Dashboard Install. So you could install one (1) dashboard along if you like (Ava, EvoX, UiX Lite, UX, X4X, X4G or XES). If not just select the "Without" option and the Flash Menu will load up right away without installing anything. Btw. this installer will install nothing if you don't wish (The only thing you could install is a Dash anyway). Not even XBlastOS or EvoX which both run of the DVD. So you will just leave with a Bios folder on C:\ which contains the bios you have flashed. And if need you have some basic tools in the Main Menu under Miscellaneous. You also will find the option to update the MS Dashboard to the lates version (5960.01) if needed in that menu along with some other options. So you see, the main goal here was basicly bios flashing. No Apps, No Dah (If you don't want) and No Crap will left behind. And ofc this installer didn't touch any byte of your maybe already installed Apps/Dashes or what ever like some others do. Finaly this installer provides all the latest bioses like Cerbios, MakeMHz, EvoX TITAN etc.. Finaly one last word. This DVD didn't use a BFM on boot so it's pretty fast. And all bios MD5 check sums I know have been added to the EvoX flasher and to the Bios Checker App (Oh Dave will throw eggs at me for this). HOW EVER..... Hope you guys have a use for it. PEACE! Downloads : 1fichier : https://1fichier.com/dir/wVNkbBai Mega : https://mega.nz/folder/UN1DzDAL#CuuhnuVesotAbaZVmIZzeg
    6 points
  5. And again, here are the download links for v2.01 https://1fichier.com/?riakentdy1npo2t0zhnw https://mega.nz/file/cFtByYiJ#Mq7ON3PzniJ3NRADdtfcMCWiQxaMQ233q0Kd_ChWLIo
    6 points
  6. A new update will be releasing soon that adds support for the larger cluster sizes, and also adds support for formatting Titan HDDs. I also have a solution for unlocking now, but that isn't ready just yet.
    6 points
  7. Run Emustation from E and have the emulators, media and roms folder on a larger partition. don’t run it from F and defo not G as the seek times are horrendous the more you fill those partitions.
    5 points
  8. Thank you for being part. I'm not the important one. You all are. This site could be totally empty... yet here you are. So the thanks goes to all of you.
    5 points
  9. Yes, why do you think it would not work? The Xbox controller port is USB with an extra Yellow wire used by a lightgun. Source: https://photobucket.com/gallery/user/xphazer/media/cGF0aDovWGJveFVzYlBpbnNfenBzYzI3ZTMxNTIuanBn/?ref=
    5 points
  10. ******************************************************************** Changelog ******************************************************************** v1.1.0 (24.02.2022) - Added a MakeMHz patched EvoX m8+ F+G noDVD v1.0.2 HDPlus Bios.* - Added a MakeMHz patched EvoX m8+ F+G noDVD v1.4.3 XBoxHDMI Bios.* - Added a MakeMHz patched iND 5003.67 XISO v1.4.3 XBoxHDMI Bios.* - Added the option to launch a pure XBlastOS to perfom a netflash. DHCP and static IP are available. - Added bios categories (Cerbios, EvoX, iND & Xecuter) to keep the main menu more clean. - Added some quick infos for each bios. - Fixed some smaller issues. - Changed some things on the skin. - Changed the config of the unleashx dash which gets installed to provide full functionality. Maybe some of you just want to play games and don't want to update the HDD so here you go with a full version of UnleashX. - Updated the ReadMe.txt (Now with much more horrible english for FREE!) - Added a Changelog. You didn't saw that comming right? * Please bare in mind that MakeMHz do not recommend to flash your TSOP with the patched bioses! ******************************************************************** One word regarding future updates. I will update this flasher when: - Team Cerbios release a version of there bios.* - Team MakeMHz releases new patches.* * Both can be updated by your self very easy by just replaceing the "bios.bin". You just need to make sure to use an very old winrar version like wirar 3.0 (which I use to create the rar files). You can find a portable of winrar 3.0 in the same folder as this flasher. Or if you report something didn't work like it should. Sadly most unlikely because ppl prefere just to flame instead of reporting bugs now days. ******************************************************************** PEACE! ******************************************************************** Download folder (Pal and NTSC version) : https://1fichier.com/dir/dyFJYcXu
    5 points
  11. FUCK! And that was the problem. I am officially retarded. I wish my mom had taken it easy on the weed and wine while she was pregnant... Thanks kaos.
    5 points
  12. Here you get a shit load of pre patched EvoX files. 144 EvoX bios'es in total. These files are for 128MB XBox'es version 1.0-1.4 and 1.6/1.6b. You get these in many different versions in many flavors like: EvoX 128MB (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX 128MB 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX 128MB HDplus (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX 128MB HDplus 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX 128MB XBoxHDMI (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX 128MB XBoxHDMI 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB UDMA2 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB UDMA2 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB UDMA4 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB UDMA4 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB UDMA5 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB UDMA5 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB HDPlus UDMA2 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB HDPlus UDMA2 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB HDPlus UDMA4 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB HDPlus UDMA4 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB HDPlus UDMA5 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB HDPlus UDMA5 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB XBoxHDMI UDMA2 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB XBoxHDMI UDMA2 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB XBoxHDMI UDMA4 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB XBoxHDMI UDMA4 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB XBoxHDMI UDMA5 (256kb/512kb/1024kb) (noDVD/yesDVD) EvoX Titan 128MB XBoxHDMI UDMA5 1.6 (256kb/512kb/1024kb) (noDVD/yesDVD) ******************************************************************************* Some infos about the patches I used: Titan Patch Version: 1.1.0 MakeMHz XBoxHDMI Patch Version: 1.4.3 MakeMHz HDplus Patch Version: 1.0.2 MakeMHz EvoX 128MB Ram Patch Version: 1.0.0* *Could also be v1.0.1 how ever, it's the latest m8plus_true_128MB_fixed.ips. ******************************************************************************* All these bios'es are sorted* and ready to use with XBlastOS or any other flasher which requires that the bios is named bios.bin which has to be in C:\bios (C:\bios\bios.bin). Note: YD = yesDVD and ND = noDVD*. (*Yes you can still boot/cold boot any DVD you like with it!) All these files are also packed as bios.rar files using winrar 3.0. So you could unpack these with UnleashX etc.. (Only of interest if you go to use these of an installer). That lead me to one thing. If you are one of the last ones who creates installer, feel free to use these files on your disc. ******************************************************************************* Credits and a HUGE thanks for the patches fly out to: MakeMHz and Gaasedelen. And also a HUGE thanks to Donnie-Burger for testing. ******************************************************************************* And don't forget to suppport the Devs! Buy'em some coffee because nothing works without coffee! Visit : https://github.com/gaasedelen/titan https://github.com/MakeMHz ******************************************************************************* Download Folders: Mega : https://mega.nz/folder/JFlR2Q5C#lxK9TfF_sgGxl2gPI4uqIw 1fichier : https://1fichier.com/dir/cdrhapgD ******************************************************************************* PEACE! EDIT: How to update your ram on a XBox 1.6/1.6b :
    4 points
  13. 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
    4 points
  14. Alright. Droping a non final bios pack. (There is only the 1.0-4 & 1.6: " EvoX Titan (UDMA2/4/5) MakeMHz XBoxHDMI 128MB " patched bioses missing (So for the old HDMI thingy thing).) ATM 108 pre patched bioses in total right now. And ofc I will see that I patch the ones for the old HDMI asap. And a new updated version of the OGXBox Bios Flasher is also on the way. ^^ Download : https://1fichier.com/?hq4acxhna8j0wxsdvztw EvoX 128MB EvoX 128MB 1.6 EvoX 128MB HDplus EvoX 128MB HDplus 1.6 EvoX 128MB XBoxHDMI EvoX 128MB XBoxHDMI 1.6 EvoX Titan 128MB EvoX Titan 128MB 1.6 EvoX Titan 128MB HDplus EvoX Titan 128MB HDplus 1.6 All bioses are available as as yesDVD (YD) and as noDVD (ND) version. The TITANS are available in UMDA2 + 4 + 5 (So in UDMA11) And you may guessed it, they are also available as 256kb, 512kb & 1024kb version. Credits and a HUGE thanks for the patches fly out to: MakeMHz and Gaasedelen. And also a HUGE thanks to Donnie-Burger for testing.
    4 points
  15. Jig idea: generic stencil for 0.76mm balls at 1.27mm pitch, with unused pads masked off using kapton tape. Since the interposer boards are 1.6mm tick, I surrounded it with PCBs of identical thickness, secured onto an ABS sheet with (thin) double-sided tape. The interposer squeezes firmly in between the surrounding boards. A few overlaying strips of kapton briefly elevate the stencil. This gives the stencil some vertical clearance for the balls to fall through, and ensures the flux on the board doesn't touch the stencil. Regardless, I highly recommend cleaning off the stencil after every board for the best results. If balls don't fall through on the next one, you should've cleaned it. After pouring on the balls, I use a very soft ESD brush to spread the balls. They balls are not encaged so I used a very light touch, or else I'd be finding solder balls all over the place for months. With the balls placed, lift the stencil and manually repair any imperfections. You can see the bottom-left ball didn't make it. After having worked on some 0.2mm BGA stuff recently (not fun), manually placing 0.76mm balls is no longer any issue, even for pads that have 8 surrounding ones. On to the hotplate for attaching them. I highly prefer IR over hot air because the balls don't move. With hot air, if you have just the tiniest bit of excess flux, balls start drifting freely. Repeat... and after about 2 hours the work came to an end. Surely there's better ways to spend your Saturday but ultimately, it's good to have it done. Not perfect, but with a small (say airbrush) compressor and simple paste dispenser you can place drips very quickly, with reasonable accuracy, and reasonably similar amounts of paste. So I'd say it's fine.
    4 points
  16. I don't like that the Startech SATA-IDE adapter doesn't have a case, so I designed one for it, and thought I'd share it. It's printed in two halves and snaps together (if all goes well). sata-adapter-case.stl
    4 points
  17. sweetdarkdestiny you are awesome, thank you its one of the best installers I've used. If anyone needs an installer or wants to try something different this is great i recommend you take a look
    4 points
  18. Has anyone seen this? After talking to a well known scene member he says its legit. up to 8tb hdd and .iso supported. From xbox scene forums: "This is a new custom bios with all existing and new features implemented by the team.While we may share some similarities that can be found in bioses such as config loading, custom colors etc, our solution will be different compared to all existing solutions.In addition new tools will also be released to take advantage of some of the features we have implemented.With our custom LBA support we now support hdds up to 8TB in storage size.No more 2.2tb limitations and file corruption.***8TB size limit may be expanded upon again in the futureMore info will be made available in due time Everyone loves a little ISO in their life. So why not add it natively into our bios.No more patching Bioses with hacky ASM, Diskutilities, Dashloader or Nkpatcher.With Cerbios just boot your console select your favorite game and enjoy endless hours of fun.Existing attach.xbe compatible.Check out the videos below of two problematic games working flawlessly as ISO and on 128mb hardware using Cerbios.https://emalm.com/?v=WU9GVhttps://emalm.com/?v=RNwC3But why should I use ISOs over HDD dumps?Well with our custom LBA support for HDD up to 8TB there is no excuse about not having enough space.ISOs do not have file length limitation like some HDD rip games do, so no patching or truncating of file names is required.All DRM checks pass as ISO (Harry Potter).More info TBA" Cerbios Alpha V1.zip
    3 points
  19. Last week I purchased a nice OG to revisit a console that I'd had so much fun with 2 decades ago and to do some modding on. I set out to finally recreate one of those Friendtech/trusty/n64freak consoles that I'd wanted to do for a long time, but unfortunately never followed up with. This was made infinitely simpler after n64freak opened up sales of his bare interposer boards, so now the daunting amount of work for engineering these boards myself from the Friendtech patent file and datasheets can be skipped. I sourced the components for the clock switching circuit on the interposer, which totaled an astonishing €5 from Digikey, while I needed to spend €50 to qualify for free shipping. This quickly spiraled out of control, I ordered everything x10... There's another 10 CPUs coming my way and there's a 10-high stack of never-been-opened xboxes behind me already. While awaiting components to arrive, I've been reading about this upgrade and this left me the impression that these CPU-upgraded consoles at some point were highly sought after. I'd like to gauge current interest and am trying to get global idea of what these units should yield when sold. I was thinking of offering the following for €275: - Clean motherboard with CPU upgraded to a 1.4GHz/512kB cache Tualatin using n64freak's interposer - RAM upgraded to 128MB by installing the 4 additional chips - OpenXenium modchip installed (or only with a flashed BIOS for some discount) - no PSU, HDD, DVD, case since cost of shipping twice easily exceeds sourcing an xbox locally for most locations I still have to think about a proper reliable solution for the heatsink if these boards are to be shipped. Any thoughts?
    3 points
  20. Possibly, try xbmemcheck xbmemcheck.rar
    3 points
  21. Alright. Here is the final bios pack :
    3 points
  22. ATA security commands are a bit of a pain in modern times. At least on Windows 10 (and probably 11?). As KaosEngineer mentioned, Microsoft has taken steps to prevent apps from sending ATA security commands to drives in order to prevent ransomware attacks. That said, it's still possible, but requires specific adapters and methods. I have been using this adapter to lock/unlock Xbox hard drives using my Windows 10 computer for several months: Warmstor SATA/PATA/IDE Hard Drive to USB 2.0 Adapter There are other adapters that work, but this is just the one I've been using. FATXplorer is going to be updated soon to add support for locking and unlocking Xbox drives, which is going to make everything much easier. The preview version seems to be working pretty well. Aside from FATXplorer, I often use smartctl from command line. I use the version bundled with XboxHDMUSB beta 4 (beta 3 also works fine). The commands below work and can be used before or after the upcoming FATXplorer version if released. Procedure: Open a command prompt with admin privileges (start menu -> type "cmd" -> right click and choose run as administrator). Determine your Xbox hard drive's drive number using this command: wmic diskdrive get mediatype,model,name Look for your Xbox hard drive in the list of drives from the previous command in step 2. Take note of the Name it appears as. It will be something like "\\.\PHYSICALDRIVEX" where "X" is a number. Take note of this number. Change the current working directory to wherever smartctl.exe is located. For example, I use this command: cd "D:\Console\XBOX\PC Utillities and Drivers\Xbox_HDM\XBoxHDM-2.3-Beta4\XboxHD" d: This will be different for you based on where your copy of XboxHDM is located on your PC. Check the security status of your Xbox drive using this command: smartctl --device=sat --get=security /dev/sdX Replace "sdX" with the letter corresponding to your drive number from step 3. 0 = a 1 = b 2 = c and so on. Example: if your drive appears as "PHYSICALDRIVE2", then your drive path would be "/dev/sdc". If your drive is locked, it will appear as "ATA Security is ENABLED, PW level HIGH **LOCKED**". If it is unlocked or frozen, this command will tell you that as well. Unlock your drive using this command: smartctl --device=sat --set=security-eeprom-unlock,..\eeprom.bin /dev/sdX (Replace "sdX" with your drive letter from Step 5) The command above references "eeprom.bin". In this case, the eeprom.bin file is located one-folder up from where smartctl is located on my PC. Disable your drive's password entirely using this command: smartctl --device=sat --set=security-eeprom-disable,..\eeprom.bin /dev/sdX (Replace "sdX" with your drive letter from Step 5) With the adapter I use, I cannot unlock the drive and then use it right away. I have to disable the password and disconnect and reconnect the drive before Windows will let me use it with FATXplorer. According to Eaton, this isn't a common problem. So there may very well be better adapters out there where you don't have to disable the password and re-mount it. Once you're done copying files to your Xbox HDD, use this command to lock the drive: smartctl --device=sat --set=security-eeprom-setpass,..\eeprom.bin /dev/sdX Also, if you're using a nulled HDD key, smartctl has a special set of commands that make it so you don't have to reference an existing eeprom.bin file when locking Xbox hard drives. It will just calculate the password automatically based on a generic "all zeroes" hard drive key. # Using null password: smartctl --device=sat --set=security-null-eeprom-setpass /dev/sdX smartctl --device=sat --set=security-null-eeprom-unlock /dev/sdX smartctl --device=sat --set=security-null-eeprom-disable /dev/sdX Anyways, like I said, FATXplorer will soon be updated with lock/unlock support for Original Xbox hard drives. So anyone having a tough time using these commands should just wait until Eaton releases the new version.
    3 points
  23. The Theory There are some awesome scans of the Xbox motherboard online for versions 1.1 and 1.6 (they have a sickmods.net watermark). I traced all the signals of a RAM chip and found these results: A0 - A11 address pins are connected to the same pins of the chip under it BA0, BA1 bank select pins are connected to the same pins of the chip under it Same for CK, ~CK, CKE, ~RAS, ~CAS, ~WE, VREF, MCL, and DQS However, the data pins DQ00 - DQ31 are in reverse order The data mask pins DM0 - DM3 are also in reverse order Since both the data pins and data mask pins are in reverse order, we can reverse both and achieve a compatible interface The chip select pin ~CS is unique for each RAM chip After this, I started tracing the ~CS signals back to the northbridge/GPU on the 1.1 motherboard. Then, I found the same pads of the northbridge on the 1.6 motherboard. Luckily, all 4 of the CS pins are exposed on the bottom of the board! At that point, I had to confirm that the 1.6 northbridge wasn't actually incompatible with the extra RAM. The chip is labelled XGPU-B which is unique to the 1.6. Maybe NVIDIA removed the extra chip select logic to save on die area? So I connected up my scope to 2 CS pins of the existing chips and 2 CS pads on the bottom. My expectation was that during the 128MB RAM test, the existing RAMs will be deselected most of the time and so their CS pins would be high. During normal operation, the extra chips should be deselected. I don't have any scope screenshots, but here was my setup with the scope probes and flying wires. That was 3 weeks ago before I ordered the extra chips from China The experiment confirmed the expectation and the rest is history.
    3 points
  24. I just posted the question asking the developer of the Titan patches for M8plus if a currently formatted hard drive will need to be reformatted or is Titan able to work with extended partitions already present on the hard drive. Awaiting their answer.
    3 points
  25. If that's the case then its not really a huge selling point for the bios. The attach.xbe method has been around for ages, nothing new. I guess the real "Big" selling point for Cerbios is the LBA48 improvements for the 3tb+ support. Also maybe the "Dual HDD" mode I suppose. If they can add UDMA5 to those and also Xbox HDMI+ patches then I can see this becoming the default bios for a lot of peeps including myself. I certainly wont be replacing my X3's bios with Cerbios then and I'll be doing a fresh build sometime in the future on a fresh Xbox once Cerbios leaves Beta status.
    3 points
  26. Thanks, if anyone has this problem mine turned out to be a bad MOSFET. New mosfet good as new
    3 points
  27. 3 points
  28. As I laid down in bed I couldn't contain my curiosity since I was still so perplexed that the 3 attempts after my initial successful one failed. I needed to check. The first board I used was a 1.4, the others were 1.0. Could there be a big difference in alignment between them? The top of the board sits very close to an SMD cap. You judge! On a 1.4, it's close but it fits: On a 1.0, oops, that'll elevate the interposer and certainly not benefit the soldering quality: I'm fairly assured this caused the poor BGA alignment. And so we learn. More later this week.
    3 points
  29. Modding Xboxes back in 2005 actually taught me alot about how computers work, with how similar it was to a PC. I had great enthusiasm as well. It was a big part of my life. Thank you for creating this forum, which has become an impressive repository of information and a place where very knowledgeable people like Kaos and Dave can answer questions that nobody can. The original xbox will always have a place in my heart and Iˋm glad aplace like this exists to preserve that passion and information for all of us. I never want it to die. Thanks very much to you, Mr. Admin.
    3 points
  30. Yep very easy from the UnleashX dash, in fact more correctly the UnleashX file explorer. It has built in FTP client. You simply connect the two Xboxes with a cross-over cable, make sure both are set to Static IP typically 192.168.0.2 and 192.168.0.1, and start both. You can use either as the host if each Xbox is connected to a separate screen or by a different cable to the same one. If UnleashX is not your main dash launch it as an app instead. Whether the other Xbox needs to be running the UnleashX dash too under such circumstance I do not now - never tried testing that. Just go to the file explorer bring up the context menu (White button) and scroll down and you'll find a new option to connect to any attached Xbox. There's a simple FTP connection menu where you can store the details of the machine you're connecting too for future use. The rest of it is fairly self-explanatory and if you're used to UnleashX's outstanding file explorer the operation is almost the same as normal except the right hand half of the file explorer is the other Xbox. I'm sure you can do this all though your router with everything set to DCHP too like any other PC networked devices but that may or may cause router, FTP Client and firewall problems. So, IMHO, unless you're going to be doing this regularly its not worth the effort of blocking an only occasionally used LAN port - FTP direct between the two, nice and simple. Its not that fast (understatement) but it'll get the job done and rarely disconnects in my my experience. I use this quite often as I have a chipped primary Xbox (v1.6) and I like to mirror the key folders/files and other important backups on that to a v1.1 softmod I use mostly just for that purpose.
    3 points
  31. Guess I took it a bit over the edge with the DEV version upSdate but hey - YOLO. v1.7.0 (06.04.2022) Added the option to restore the default evoxdash.xbe shortcut which by default points to: E:\Dash\UnleashX\unleashx.xbe. (BASIC) (PRO) (DEV) Added the option to reinstall the default UnleashX dashboard. (BASIC) (PRO) (DEV) Added some more copy options to the EvolutionX flasher section of the flasher. (DEV) They are now the same as in the XblastOS section. Added the option to install the EvolutionX dashboard with DHCP config to C:\ as default dashboard. (DEV) Added the option to Re-Install all apps. (PRO) (DEV) Added the option to Re-Install the UnleashX dashboard. (PRO) (DEV) Added the option to Re-Install the EvolutionX dashboard. (DEV) Added the option to backup your EEPRom. (DEV) Added the Yoshi k2005 Debug in 256kb & 1024kb bios‘es. (DEV) Added Gentoox ShALLaX v6.07 256kb bios. (DEV) Added the option to launch Config Magic v1.6.1 in the flasher. (DEV) Added the option to launch Enigma PAL/NTSC in the flasher. (DEV) Fixed two 256kb retail bios names. (DEV) Added a bios overview in the about section incl. rar file names and MD5 checksums of the .rar and bios.bin. (DEV)
    3 points
  32. And a new update. Gaasedelen released new TITAN patches for the EvoX bios 7 hours ago and here they are. Hot and spicy v1.6.0 (03.04.2022) Added the new updated TITAN v1.1.0 patched EvoX bioses. (PRO) (DEV) https://github.com/gaasedelen/titan/releases/tag/v1.1.0 Added the option to flash your bios with EvoX. (DEV) For a better overview EvoX & XblastOS have there own sub menue here. Added some Complex debug bioses. (DEV) Fixed some typos ( Guess there are a lot more so it’s a never ending story. ) No changes were made to the BASIC version, so if you can deal with typos there is no need for a download. Download sites (Pal and NTSC version) : >>> See first post! <<<
    3 points
  33. EA controller came in today, can confirm that it DOES work with the green receiver
    3 points
  34. This guy did it. And a clean room https://northridgefix.com/product/portable-dust-free-clean-room-with-green-and-white-light/
    3 points
  35. You can use eaton-works.com's FATXplorer 3.0 Beta to format and read/write files from/to a new hard drive to prepare it for the Xbox. (Edit: See Hazeno's Tutorial - FATXplorer 2TB Preload Guide) As for the IDE-to-SATA adapter, I suggest using one with Marvell's 88SA8052 IDE-to-SATA bridge. Startech's IDE2SAT2 or Delock's #62510 adapter. (Edit: Note there are cheaper IDE-to-SATA adapters that work but I prefer not to use them myself.) For reliable SATA hard drive operation, you'll also need a high-speed 80-wire 40-pin IDE cable - length 24 inches to replace the stock IDE cable. I suggest ChimericSystem's Custom Xbox IDE cable. However, starting Dec 20th they are closed for a few weeks and you can't order or see it on their web site.
    3 points
  36. Already solved? OK, I was a bit slow at the topic. How ever, instead of using WinSCP just use FatXplorer 3.0 and copy your files right on your PC to your XBox HDD. That way you are much faster (~1/2 of the time saved)
    3 points
  37. Have you formatet your HDD twice? ( If not you have to! ) Does XBPartitioner shows a error [ER] on your partition?
    3 points
  38. The updated and fixed version of the FatXplorer + XBoxHDM is now online. Direct links: https://mega.nz/file/4ENnEQYC#9FB7tYRyjfhdghyColUWTQUNbKFYUoU-3UXfhsRV2-c https://1fichier.com/?kinvner9q3c4dy7yiobz
    3 points
  39. Here is a little beginner tutorial about how you can overclock your EvoX bios using WulfyStylez XBOverclock tool. First of, download the XBOverclock tool. Download incl. bioses : https://1fichier.com/?qdelzlqfg0dp58scr67a Download from Github without bioses : https://github.com/WulfyStylez/XBOverclock Now extract the file. You should now have a folder called “xboverclock”. (In case you downloaded my upload. If not rename the folder to xboverclock) For this “tutorial” we place the extracted folder in C:\ ( C:\xboverclock\... ) Screenshot 1: https://imgur.com/a/MmkTuzo Now open a command prompt and enter the folder by typing “ cd c:\xboverclock “ and hit enter. You can now check for the files if you want by typing “ dir “. You should now see all the files in that folder. Screenshot 2 : https://imgur.com/a/a35fEkO Now we are going to create our own overclocked EvoX bios. This is the command with STOCK values : " xboverclock -nv 233 -fsb 133 -o EvoXm8plusOC.bin EvoXm8plus.bin ". NOTE: “ -nv 233 ” is the GPU. Base value of it is 233MHz. Change this value to what ever you want but don’t go crazy! Best is to rise it step by step 1 or 2 MHz and test the bios. “ -fsb 133 “ is the value for the CPU FSB. In our case it`s 133MHz. Like mentioned above, don’t rise this value to much. #Babysteps! So go with 1 - 2 MHz at a time and test the bios. “ -o EvoXm8plusOC.bin EvoXm8plus.bin “ This will tell the tool that it should use the bios “ EvoXm8plus.bin “ and output the overclocked bios as “ EvoXm8plusOC.bin “. So let’s recap with a little example line and a 2 MHz overclock for the CPU-FSB & GPU. A valid OC command could look like this : “ xboverclock -nv 235 -fsb 135 -o EvoXm8plusOC.bin EvoXm8plus.bin “ Now it’s time for you to decide what values you like to test. For this tutorial let’s grab the line from the note above and type in your command prompt : “ xboverclock -nv 235 -fsb 135 -o EvoXm8plusOC.bin EvoXm8plus.bin “ and hit enter. You should now see the output like in the screen below. Sceenshot 3 : https://imgur.com/a/joL0krn You made it. The xboverclock folder should now contain a new bios file named EvoXm8plusOC.bin which you can flash to your mod chip. Note: Do not edit this bios now with e.g. EvTool because that will reset the OC to defaults. So in case you need to make changes to the boot order do it before you overclock the bios! And some words of warning. Don't expect any wonders. In most cases you will not benefit from the overclock. It’s mainly made for emulators and not for games. In some cases you gain 1 or 2 frames in games and in some cases games will run to fast even with this small overclock. So you would need to patch these games xbe’s for the new clock speeds. And yes, it’s a lot of work testing out how far you can go with your overclock (every XBox is different which means, it works for me but, it may didn’t work for you) and a lot of trail and error which in some cases could brick your XBox. So do never ever flash these bioses to a TSOP – NEVER! Do not flash these bioses to a single bank mod chip like Aladdin, LPC/Cheap Mod etc. without having a external flasher on hand to flash back a working bios or without having a second SST chip laying around to perform a hot flash. This is a SERIOUS warning and no joke! So bottom line, is it worth the hassle? Nope. It’s more or less a proof of concept and something to play with for us neerds and nothing for the casual user. But that’s just my opinion and you may think differently about that which is totaly fine. Finaly we have reached the end of this small “tutorial/overview”. Have fun and please don't brick your XBox by doing stupid things! PS. Here is a short YT video I have made where you can see all the stuff above in action instead of pictures : https://www.youtube.com/watch?v=pMNSfDFsiQs PPS. You can download this “tutotial” here as PDF if you like (Incl. Pictures :D ) : https://1fichier.com/?jahpi6lewhdxynf5va2f PEACE!
    3 points
  40. No, the MS Dash will be installed by default when you set up a new HDD. You can launch the xboxdash.xbe by using the file explorer in X4G. It should be also possible to place a shortcut (if not already there). Every bios has default path's. On my installer there are planty of pre configured bioses for every dashboard so no need to edit something. Just flash a X4G bios and you are good. The major difference, when it comes to the boot entires is, that the iND has a config file (like the Xecuter) where you can edit the path of each dashboard. The EvoX dosn't have that and to change the path for the bios you would need a tool called "EvTool". It's very easy to use and not much more complicatet like edeting a txt file. Down side for the Evox bios is, if you change something you would need to reflash the bios. For the iND you just edit the config and reboot. The EvoX though boots up a little bit faster because iND & Xecuter needs to load the config first which coast you ~2 sec. The 5003 XISO has some patches and the option to mount ISO files more easily using the included Dashloader app. Here is the read me ot the iND Bios Bios has been patched to fix the white+back shutdown bug and also the Ram speed patch has been applied. ( Patching done by xbox7887 from discord, great guy. ) XBL Patched by me, but original 5004 patch done by kl0wn. You may ask why? when there is 5004, well 5004 cant have XISO support patched into it, 5003 can. So if you want to load XISO off the HDD now you can and not have to worry about the shutdown bug. Dashloader: This is required for the XISO loading as ind-bios loads CDrom0 instead of CDRom1 like Softmods, so I have to do the launching of he xbe eg... It also includes the kernel patcher (XISO support, softmods the kernel) and the dismounter, so it acts just like a HDD game would. (its 1 xbe that does it all) Using Dashloader Customizer you can toggle whether it dismounts the XISO on IGR or not. ( Triggers+Back+Start to go back to the dashboard, Triggers+Back+Black to reload the disc ) Shutdown Bug Fix: ; inject over 24 bytes of scratch space at 00007C31 until 00007C49 ; original bytes = 8B15F0BA03808B9204BB038081E2FF0000005023C23BC258 ; assembled bytes = 508B430825FFFF00003DFFFF0000587407B8F37C0180FFE0 ASM Code: push eax mov eax, [ebx+8] and eax, 0FFFFh ; XINPUT_GAMEPAD.wButtons.XINPUT_GAMEPAD_LEFT_TRIGGER | XINPUT_GAMEPAD.wButtons.XINPUT_GAMEPAD_RIGHT_TRIGGER cmp eax, 0FFFFh pop eax jz next mov eax, 80017CF3 ; no_reset2 jmp eax next: Ram Patch: ; inject over 12 bytes of scratch space at 00022C52 until 00022C5E ; original bytes = C3CCCCCCCCCCCCCCCCCCCCCC ; assembled bytes = B9FF0200000F32B0060F30C3 ASM Code: mov ecx, 0x2ff rdmsr mov al, 0x06 wrmsr No Xbox Live Patch: ; Disabled Xbox showing as Debug Hardware ; inject over 7 bytes of scratch space at 00009484 until 0000948A ; original bytes = 830DA0DA038002 ; assembled bytes = 90909090909090 ASM Code: nop nop nop nop nop nop nop ; Jump patch section ; inject over 1 byte of scratch space at 00023F23 ; original bytes = 75 ; assembled bytes = EB ASM Code: jmp short loc_80033F34 ; Jump patch section ; inject over 1 byte of scratch space at 00023F6F ; original bytes = 75 ; assembled bytes = EB ASM Code: jmp short loc_80033F91
    3 points
  41. Once you have setup the HDD then load the installer disk and look in the live apps section, there is a program called XBpartitioner 1.3 load that and it will show all the drives, there will probably be a ER on partition 6 and or 7 Start by pressing B to distribute the space of partitions 6 and 7 evenly the highlight partition 6 and the D-Pad right to reduce the size by 2gb (925.76gb) and repeat for partition 7, Now press the start button to format the HDD. When the format is complete you need to power cycle the Xbox (power off then on) and reload the XBpartitioner 1.3 and highlight partition 6 (F drive) and increase the size using the D-Pad left to 927.76gb and repeat for partition 7 (G Drive) and press start to format. The reason for doing this way is there is a bug in the XBpartitioner program. Now you can start to copy your games to the HDD. Cheers SS Dave Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.
    3 points
  42. I have uploaded it to my Xbox Repository at https://1drv.ms/f/s!Ao7Z5kIDEKUmguAP8ELOjH_Pf6PCDw Look under Auto Installers > TruHeXEn
    3 points
  43. I have my version of PES5 new balls my ibrox stadium that I made donkeys ago for PES5 its teams done, names etc… also patched xbe to remove the flicker filter and patch in the crowd on wide views. On new menu to look like PES6 since we never got it same with ingame graphics like play on icon etc… Can’t remember if the boot packs I helped make all those years ago are in it. Would need to install it and check.
    2 points
  44. Depends which BIOS flashing software was used to flash the v1.1's TSOP. Not all of the flashing software fills the flash memory chip. Some write the one copy of the dot bin file leaving the rest of the flash chip empty. GentooX Loader is one that does not write multiple copies of the BIOS to fill the flash. If that tool was used, then the 1MB TSOP now contains: 256KB CerBIOS 256KB Empty (0xFF filled) 256KB Empty (0xFF filled) 256KB Empty (0xFF filled) Instead of 256KB CerBIOS 256KB CerBIOS 256KB CerBIOS 256KB CerBIOS You should be able to solder two wires to force access to the first 256KB BIOS. Like used to fix a COMA v1.0 or v1.1 console. Xbox Coma Console (archive.org)
    2 points
  45. For already chipped/TSOP'ed XBox'es you can use any installer. This here is made for those who dosn't even have a TSOP flashed XBox and want to avoid to softmod first,
    2 points
  46. Here's another forum thread at xboxscene.org: Info: Dvd Dongle + Controller At Same Time (xboxscene.org) Pictures are missing but I'm going to see if I can track them down and add them to this post. Edit: Not so easy, the missing image(s) were hosted at imageshack.us and are not found on the Wayback Machine. archive.org does have a HUGE repository of archived images from there but you have to download large sets of images, extract the content and hope to find the ones you are looking for. I'll try a different tactic and see if they were archived along with the web page from xbox-scene.org. Edit: No luck so far...
    2 points
  47. Make sure in your LCD.xml you change LCD.timeWide21, LCD.timeWide22 with something else as this is bugged out in xbmc with xenium chips
    2 points
  48. As a rule the Xbox will not boot with failed cap's in the PSU and if there is failed or failing caps on the main board the Xbox may boot but could have issues with video and or it may randomly shut down. The chance for a capacitor exploding in a Xbox is extremely low although it can make a mess if they do explode but in 99% of cases I have seen items with exploded caps in items there was no damage to the boards and the most common cause of the caps exploding was from over voltage (like using a 6.3 volt cap on 12volt or more) and if that's the case then you have bigger problems. The most common caps that need replacing are the three or five next to the heatsink followed by the one or 2 next to the 12 or 20 pin power connector. Cheers SS Dave Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.
    2 points

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.