Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


HDShadow last won the day on September 9

HDShadow had the most liked content!

Community Reputation

63 Excellent

About HDShadow

  • Rank
    Experienced Member

Recent Profile Visitors

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

  1. Error 9 is said to be a rare Xbox flagged up fault. Never seen it myself until today. My newly successfully pin-headered v1.2/1.3 is destined for a TSOP. The only reason I put the pin-header in was to use the Aladdin chip to allow me to get the eeprom from the Xbox which I couldn't do almost any other way because it came with only an Error 16 HDD when I bought it. I used another Master HDD and Chimp 261812 to fix the Error 16 HDD as Slave BTW the Chimp 261812 Error 16 Fix option did not work. It just spewed out an endless stream of hdb error lines. I let it run for 15 minutes b
  2. Xplorer360: when you open it and choose the Drive > Open > HDD or Memorycard you should see a "Partition 0" in the left pane. Click on that to see the contents of the flash drive in the right pane. But if you've only just opened it, of course, nothing is going to be there. Xplorer360 is used to transfer the game save exploit and installer to the flash drive from your PC. Where this "4 NTFS folders" thing comes in: I assume that is a typo and should be NTSC. I believe it refers to the four exploitable games: MechAssault, SplinterCell, 007:AUF, and TH4. You do not need them
  3. As I've been TSOPing and chipping recently using customised BIOS I thought it would be a good idea to add the MD5 hash info to all the programs that can make use it: XBMC, EvoX and, of course, BIOS Checker. All three have slightly different syntax requirements apparently but whatever I did I couldn't get BIOS Checker to recognise the custom BIOS I'd added. The cause and solution turned out to be very simple: I was pasting in the MD5 code from EVTool, which has an option to copy it to the clipboard. Sensibly it uses lower case letters in the ID string and after half a day wasted, thinking
  4. What's wrong with Super Glue? If the tiny bridging wire is sitting on top of the two points (v1.2 - 1.4) a small drop of superglue would lock it into place. It is possible to get the bridging wire resting on top, its what I tried initially with the soldering. I thought if I just melted the solder each end it would connect but each time I tried that the bridging wire preferred to attach to the soldering iron or I knocked it off before the solder was set. As said the Super Glue idea was only a passing thought.
  5. Retail BIOS for the Xbox are available to download so a TSOP can be reverted back if necessary. I've not done it myself but when you backup your softmod eeprom using the EvoX tool it also includes the original BIOS.bin too. I assume that could be or even should be used but I'm not a BIOS expert at all so you'd need one of the guys here who are to confirm that. Chipping too is reversible; if all you've done is fit a pin header rather than solder it in permanently a chip can just be removed and the D0 desoldered and that's it. You'd need to have a locked retail MS dash installed HDD for it
  6. I did say "ideally" in reference to bridging the required TSOP points. I was considering the use of conductive paint as the alternative. I've tried it using just some Kynar wire and tape and I even considered super gluing a minute bridging wire in place but thought better of it. Other cheaper methods are indeed possible but that's not my main concern about TSOPs. It is the significant potential to render the Xbox unusable unless you fit a chip. Yes, there are chips that will allow you to fix the TSOP problem but they cost more than a replacement Xbox which I think is a genuine a cons
  7. It does require a fully working DVD drive to be able to run the exploitable game (Splinter Cell, 007 AUF etc). You can prepare a softmod HDD using Xbox HDD Maker or on another chipped Xbox (my preferred method) but you still need the eeprom from the Xbox concerned to lock its HDD. You can't get that, at least not easily, unless you've softmodded the Xbox first............which requires a working DVD drive. An eeprom reader can bypass that problem but that is a lot of hassle. There is also the problem that if your DVD drive dies completely on a softmodded machine it won't boot an
  8. For the first time I'm using a Seagate 2.5" IDE HDD (80GB). I'd decided to use it in my newly Aladdin chipped Xbox principally because I discovered it could not be locked (as Slave) after I'd successfully used Chimp 261812 to clone a softmodded HDD to it. Retried and Chimp kept on reporting the drive could not be locked and indeed after I'd changed it to Master I had error 5 on that Xbox. Once the other, Aladdin chipped, Xbox was up and working I fitted that same unlocked 2.5" HDD and used an AID disc to install a chipped UnleashX dash. Everything works fine One of the things I
  9. Used EvoX to do the flash and all went perfectly. Interestingly the IGR that was not working at all when using the Aladdin's BIOS is now working too. Only minor matter is that I didn't realise the Trade Mark Symbol was going to remain displaying in original green so I'm going to have to reflash with that option unticked as it doesn't look right with the red theme customisations I've used. On the customisations issue I'd like advice on importing a replacement for the pink/purple Evo X logo. I've followed the advice supplied with the EVTool and now have a 128x128 DDS saved using t
  10. I'm a softmod fan so I'd recommend it to any noob but only as long as it practical (DVD drives dying are the biggest threat) and you're the only one ever going to use the Xbox concerned. The greatest danger to a softmod comes from the uneducated fiddling with the C and E drives not anything inherent with softmodding. Indeed all the most recent softmods address this issue trying to make the installation as bullet proof as possible. The fact is if you let other people, particularly small people , use your softmodded Xbox they will stuff it up eventually. The solution is simple use the
  11. I meant to ask about that DVD setting too as I noticed that the TruHeXEn "nodvd" BIOS didn't fill that box. Is that really a fault with the BIOS settings? I assumed the reason was that without a working DVD drive that setting is irrelevant. But I can see it as being a better choice to use a "nodvd" BIOS which will work normally with a working DVD should one ever be fitted. So thanks for that advice. Just used that ^ BIOS template (thanks) and this is how the EVTool shows my customisations now:- All good and ready to flash?
  12. Really just double checking I've done everything correctly before going ahead with the flash on an Aladdin XT Plus2 in a v1.2/1.3 Xbox. It is an edited version of TruHeXEn's evox.m8plus.f.c.137.nodvd.bin. Changed the Xbox logo etc to match the Aladdin red chip theme, might modify this later if it doesn't look good. Also thinking about designing and importing another EvoX logo - details on how to do that are included wit the EVTool but if anyone has any additional information on this please share. Major changes are the boot priority: C:\evoxdash.xbe is default but I've chan
  13. I think this is the best place for this. Just informational stuff about AID versions which might be of interest. I've been girding my loins for a custon Evox M8+ Aladdin chip flash and I thought why use AID as that has BIOS files and a flashing tool (ie. uses the EvoX dash). But in the AID installation I have on that particular Xbox I couldn't find the flashing menu. I looked at the config.xml and there's a whole load of stuff for copying BIOS to C, E, F etc but no actual flashing tool. The AID download I used (not from here) and the accompanying version info shown it just as v4.53
  14. If you're using a v1.6 Xbox and there are specific games which are refusing to display in 480p then you will want to see this .
  15. Just a thought - have you tried running XBPartitioner v1.3 and seeing if there is any ER (error) shown against the extended partitions? Its a 2TB HDD and my first thought when anyone has problems and they're using one is that it wasn't correctly formatted originally. Would it not be a good idea just to check that, even if only to exclude that as a possible cause of the problem? If it is nothing suggested here is going to be of any use.

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.