Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


HDShadow last won the day on March 31

HDShadow had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

HDShadow's Achievements


Collaborator (7/14)

  • Reacting Well Rare
  • Dedicated Rare
  • Conversation Starter Rare
  • Very Popular Rare
  • First Post Rare

Recent Badges



  1. Something definitely is not right if you're using the very noisy x5 fan speed and the reported temperatures with an UnleashX dash are still 60°C+.
  2. What I meant by checking the airflow around the console is just to make sure the Xbox has plenty of space around it and can vent the hot or warm air away from the console. The air being expelled will not be at 61°C if that is what you thought.
  3. It is dependent on the airflow around the console, ambient temperature and fan speed but those are not untypical of what UnleashX will report in hot weather 30°+C with the fan at the default setting x1 (20%). I've never had to increase the speed of the fan beyond x2 (40%) to keep the temperatures <60°C (just) even on the hottest UK summer days as there were this year with ambient temperatures often above 40°C. Check what XBMC reports under the same conditions and if after a couple of minutes that is still showing temperatures >60°C with the fan at x2 (40%) then there is cause for concern. But if not don't worry too much. Keep an eye on the temperature and it does not drop in cooler ambient conditions or goes above 65°C action is needed. No doubt some here will say you should replace the thermal paste but as others here will attest that rarely has any dramatic effect on the reported temperatures.
  4. I'm thinking it has got to be a weird BIOS thing if you can see it using HeXEn's file explorer from disc only ie. not any other way. I'd suggest not moving stuff around until we're certain what is going on but I see no problem in you using HeXEn from disc to get FTP access and backup everything on F:\ to PC. The content of E:\ is accessible, yes? Try creating an E:\UnleashX or E:\Apps\UnleashX folder and copying in an UnleashX dash "default.xbe" (copy it from HeXEn if needs be - HeXEn > Dash > UnleashX > unleashx.xbe and just change the name to default.xbe). Launch that from your dash and use its file manager to check if it sees the content on F:\. Do make sure F:\ is enabled in the UnleashX main menu System > Settings > Storage > Harddisk Settings (its right at the top). If this installed UnleashX dash can not access the contents of F:\ then a BIOS problem seems a possible explanation but the best course of action to take if it is that I'm not qualified to advise on such matters. BTW when UnleashX launches it will create a default config.xml and item.xml in the UnleashX folder. The default config.xml for UnleashX v584 (the final version) is fairly sparse. It only contains E:\ and F:\ paths for Games and Apps but if you have either of those folders on F:\, after rebooting the test UnleashX dash, they should show up or the content list be added to E:\Games and E:\Apps respectively in the main menu content listing too.
  5. How can you launch an emulator XBE directly from the file manager? That contradicts what you described earlier. Can you see the 'missing' content in the file manager? If so it sounds like it is just a XBMC Source path issue. With a basic XBMC install the games, emulators, apps are set up as sources using just E:\ drive paths eg. E:\Apps or E:\Emulators. If the previous XBMC user settings are missing for some reason you'd need to redo ie. add the F:\ drive path locations again for those folders as sources. Under the main XBMC menu: Programs you should have an Add Source option or it can be done via the White button context menu.
  6. C:\ and E:\ free space are pretty typical and for a 200GB HDD with stuff on it 48GB+ for F:\ appears plausible. If it was empty you'd expect 170+GB. It is worrying that you can not see the content via FTP. The default 16KB cluster size for extended partitions should be good for a 200GB HDD but it might like to just check with XBPartitioner v1.3 that there is no ER (ERror) flag against Partition 6 (F). I doubt that is the problem in this case but it needs to be ruled out.
  7. If it wasn't unlocked you wouldn't be able to have booted any dash. You're talking about the 200GB softmodded HDD you mentioned, yes? What was used to softmod it? I can't think of any reason C:\, E:\ and F:\ drive content could be "effectively empty", the XBMC file manager showing nothing and the Xbox be booting at all. If you have FTP access what does that show as the content of those drives? What does mean "effectively missing" mean exactly? My thought is that whatever is wrong, with the HDD unlocked, you should use PC tool: FATXplorer and get any content backed up. I would suggest doing that before trying to fix anything.
  8. It depends if the old HDD in the first Xbox was locked or not. If it was, as it must have been for the softmod to boot, except in very specific circumstances that are unlikely to apply here, you can not just transfer a locked HDD from another Xbox to a new machine. The HDD needs to be unlocked and unless you have the eeprom backed up to PC you have problem. If the old Xbox MB was really damaged you might not even be able to use an eeprom reader to get it off the old MB. TBH doing that anyway will be more work than installing a clean, empty HDD to the the newly chipped Xbox and setting it up from scratch. Even if was unlocked - being a softmod there's a good chance it would not boot anyway unless the BIOS used was customised to do so.
  9. Those who created artwork packs might have different recommendations depending on the screen format but the size I've used for the dozens of custom icons I've created for things like homebrew games, alt game saves*, apps, emulators etc which works well with both XBMC and UnleashX is 256 x 256. Keeping the file size down below 50KB by using JPGs or 'optimized' PNG helps with the latter. It is particularly important with UnleashX as that has some sort of total dashboard menu icon memory size limit (possibly 100MB). As you approach that you'll get progressively bad slowdown at boot and icons will eventually go missing. With both XBMC and UnleashX .PNG or .JPG image files are often interchangeable, you can just change the extension. With XBMC that is more useful because certain uses require .JPG rather than .PNG. Also with XBMC .TBN (thumbnails) can be either .JPG or .PNG. You just change the extension to .TBN. It may also work for .BMP with XBMC which that supports unlike UnleashX. *Alt game save icons ie. TitleImage.xbx and SaveImage.xbx can be created from .JPG or .PNG but the PC XBX Tools program, preferred to the very crude Xbox Image Converter, requires that they're converted to a .DDS image file, of a specific type too, first. A graphics program like Paint.net has plugins to do that. Oddly XBMC's file manager won't display .XBX image files using its picture viewer whereas UnleashX will. BTW the XBX Tool is picky when file naming. Name the .DDS as a single word or number ID and, when prompted, name the .XBX to be created exactly the same. It also does not seem to like long folder paths and whilst I try to avoid working on the desktop usually for this purpose it may help resolve any error messages you may get when using this converter program.
  10. If the Xbox was modded and it sounds like it must have been or how could it be unlocked you should check for a an E:\Backup folder to see if a copy of the eeprom is in there. If not but the Xbox has exploit game saves still in UDATA check the installer: E:\UDATA\21585554\000000000000\ for a Backup folder. Its the default location for an eeprom backup save before/during/after install if another location was not specified. Otherwise you likely going to have to go down the eeprom reader route and TBH that is as much hassle as fitting a cheap chip so the latter is probably the better solution to getting the Xbox booting again.
  11. I'd be looking at the actual folder path and file names in a file explorer too. In particular, especially if you've renamed anything yourself, check for accidental spaces that have been added between or after characters/names. I noticed that in your earlier post here (although probably just a typo) you typed "XBMC - Emustation" rather than "XBMC-Emustation". It could be something like that. Other thing is: where exactly is the "default.xbe"? I ask because I have an uninstalled zip of XBMC Emustation and when unpacked on PC it is set up like this: XBMC-Emustation (folder) and inside that > .emustation (folder), system (folder), default.xbe (file), splash (logo image file). I would assume that is how it installs. If your installation does not match then that could be the problem.
  12. You don't really need one that sophisticated - a simple 2.5" HDD to 3.5" drive bay adapter caddy is all that is required. I use an Akasa two stack in one Xbox box but also have SSDs mounted in 3.5" PC bays with even cheaper types like this:- https://www.amazon.co.uk/TRIXES-Black-Metal-Internal-Mounting/dp/B00HFSMHDI/ref=sr_1_12?keywords=2.5"+caddy+internal&qid=1662726970&sr=8-12 NB. If you're going from the original IDE HDD to a SATA device of any sort you'll need an adapter of course. Its physical dimensions might affect your choice of caddy because the Xbox HDD caddy is not like a PC drive bay. It is essentially a flat tray and there is not enough height to fit some IDE > SATA adapters. With the Akasa caddy you can just use the top mount position. With the PC mentioned I used PC case motherboard hex standoffs to raise the SDD for cooling reasons but some solution like that may well be needed with a single position caddy like the other one if used in a Xbox.
  13. ^ yes. Or it was burned on incompatible disc media - DVD-R/ImgBurn recommended. Or the XISO was not created correctly from the extracted game files. What was used? Qwix or the C Xbox Tool? XISO files can be played on the Xbox directly but it is a bit of a faff:- https://www.ogxbox.com/forums/index.php?/topic/1134-xiso-playing-games-from-xbox-hdd-using-iso-images/ As for the last comment on Xemu: what works with an emulator on PC could be different from what works on an actual Xbox modded or not.
  14. I'd be wary of updating the BIOS using any HeXEn based disc here without expert advice from those who know about this sort of stuff. There are apparently problems with some BIOS on older HeXEn type discs and I think one version of 'TruHeXEn' in particular. So my advice would be to wait for advice on what tool and what BIOS to use.
  15. Wouldn't it have been better to start your own thread rather than add to this three year old one? It's not the same problem or, possibly, even a problem. It looks as if you're probably using a type chip (Aladdin?) with an v1.6 Evox M8+ series BIOS already on it. Flashing the BIOS using a HeXen disc should be a simple matter of launching the HeXen disc (DVD-R/ImgBurn) and going to the BIOS flashing tools menu. Alternatively: using EvoX or XBlast installed as apps booting either of those. That's only if you've installed a dashboard already of course.

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.