Jump to content
OGXbox.com

KaosEngineer

Moderators
  • Posts

    5,063
  • Joined

  • Last visited

  • Days Won

    479

Everything posted by KaosEngineer

  1. That is the original Surreal64 1.0 UI. Not a skin for Surreal64 CE. Looks like it requires the controller to be connected to Port 1. The Xbox I tested it on has a broken port 1 so the controller is connected to port 2 but there's no response to it in the emulator. I was able to use the IGR button combo to exit out of the emulator but no control of the emulator UI.
  2. They are from the OGXbox Theme for XBMC4Gamers. If you had the theme installed then uninstalled it then reinstall it, they do not get reinstalled. They are replaced with solid pastel-colored backgrounds. I'm not sure what the bug is that prevents the entire theme including its backgrounds from being installed.
  3. OX only has an SPI output for connection to an LCD module. There is no parallel interface required to connect to an HD44780-based module. You must use an SPI2PAR board to convert the data to the correct format. The Arduino Pro Micro is one part of an SPI2PAR2019 used to convert the OX's SPI interface's data to the parallel data format required of the HD44780 LCD module. The SPI2PAR2019 includes an spi2par2019backpack (or spi2par2019faithful) PCB to hold the Arduino Pro Micro and mounts to the HD44780 LCD module. You can use the Arduino Pro Micro by itself, but soldering is more complex as stated in the SPI2PAR2019 github.com repo Option 2. Is yours an Arduino Pro Micro Leonardo 5V/16Mhz version?
  4. Is the jumper for a 1.6 present on the Open Xenium modchip.
  5. They need the Xbox Softmodding Tool's extracted content from the Installer Variant / XBHDM Build.zip file instead of the stock 5960 dashboard fileset added to the C drive with FATXplorer 3.0 beta. XBHDM Build's content is a no-original-game-disc-required bootable Xbox Softmodding Tool installer. Next, lock the hard drive/SSD before installing back in the Xbox. Boot the console. The installer will load. Follow the onscreen instructions to complete the softmod install process.
  6. That's why there's a small hole to access the manual eject mechanism to the left of the eject button on the front panel. Use a straightened-out paperclip to press on it to slightly open the DVD drive's tray so you can pull it out further to remove the game disc. People don't RTFM! Although if it was a Philips drive, the manual eject mechanism's access location is at a different location not documented by Microsoft. llamma.com archived webpage: Ejecting DVD drive Manually
  7. Post a picture of the modchip showing it and this mystery wire's connection.
  8. I've never seen that red X/checkmark logo before. It must be booting an old version of EVOX BIOS that does not have the err16 patch to skip the clock check on bootup. Does the modchip have a switch on it? If so, flip it to the other position and boot the console. Does a completely different BIOS appear?
  9. Change it how much? To something completely different, no. Change colors, yes with EVTool. Cerbios, the latest modified BIOS for an Xbox, is what you are looking for to do anything more than simple color changes or turning off displaying the startup animation - the time it takes to play still occurs with a blank screen visible.
  10. See if you can find a way to use the Pico as a JTAG Programmer.
  11. Could cause both. Games definitely and homebrew apps create files/folders in E:\UDATA to run. If creation fails, so does execution of the game/app. If backup up the eeprom with Evoxdash, depending where Evoxdash is installed. It too may not be able to create the folder and files for the Backup operation.
  12. That's not what it's saying and what is saying is a bunch of bull anyway. Wherever evoxdash's dot xbe file runs from is where the backup folder will be created to store the 5 files Evoxdash's Backup menu option creates: bios.bin disk.bin eeprom.bin diskinfo.txt hddkey.bin
  13. PriMas is the Xbox HDD. Press Tab to switch to the right-hand pane. Move down to C, E or F press Enter to open that folder/drive/partition on the Xbox hard drive. Move up to .., press Enter to go up a directory level. Press Tab again to switch back to the left-hand pane. /CD/C is the C folder on the bootable XboxHDM CD where you place the content to copy to the Xbox's C drive. However, it has a limited size. One or two hundred megabytes can be stored there.
  14. Everything I find says to use usbjmicron setting, not sat. Try using the XboxHDM23USB beta 3 and its command line app smartctl.exe. Edit: Edit the files checklockhdd.bat, unlockhdd.bat, and lockhdd.bat to add -d usbjmicron for every line that calls smartctl.exe. Place the eeprom.bin file in the folder where xboxhd.bat is located after extracting XboxHDM23USB from the zip archive. https://www.mediafire.com/file_premium/aqc8lyhrrlwc6rj/xboxhdm23usb-Beta3.zip/file
  15. Is the 80-wire 40-pin IDE cable a custom cable made for the Xbox or a standard PC cable? If a standard PC cable, set the adapter to MASTER. (Edit: However, Samsung DVD drives for some reason don't work well with a Startech IDE2SAT2 adapter - the cause - unknown at this time.) Installing a standard PC cable end-over-end defeats cable select of a stock PC cable - it no longer works.
  16. Find the adapter's idVendor and idProduct values. Use usbviewusbview.exe to do so.
  17. Truhexen doesn't boot into Linux. It loads UnleashX - a Xbox replacement dashboard just like Rocky5's Xbox Softmodding Tool does. They use a different skin to change how each looks. Edit: I see what you are talking about. The word Linux appearing under the big X logo at the end of the startup animation. You cannot boot the TruHexen disc after swapping hard drives. The console is no longer modded. The softmod that allows unsigned code to run is installed on the original hard drive, not the new one. You must be hard modded to use the method shown in the video you posted the link to.
  18. When you power on the console, hold the power button until the eject ring flashes, then see if you can get to the flash BIOS menu in evoxdash.
  19. This MD5 hash value, 0x09A1D434DBD7197E7C3AF8A7C28CA38B, is for 1MByte of 0xffs. An empty 1MB flash chip???
  20. I believe that's it. Once the eject ring flashes, the modchip is write-enabled. After that happens, try evoxdash's flash bios option again to see if the manufacturer and product IDs appear.
  21. Ok, it has the Flash = line for an SST 49LF020A. What about the Current= line? There should be a line in evox.ini that reads: Current=<hexadecimal MD5 hash of the currently running/loaded BIOS/Kernel> Seems the Duo X2 is write-protected. I wonder if it uses the same trick that some Aladdin modchips have. You must hold the Power or Eject button, whichever activates the modchip to load the BIOS flashed to it, for 5-10 seconds to write-enable the modchip. Try holding the button for 10 seconds then run Evoxdash's flash bios menu option. Does it now display the ManufacturerID and ProductID?

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.