[Problem Softmodding]

7 hours ago, shadow0191 said:

Yeah both save files are on the hard drive.   Worked late today so didnt get a chance to try the older softmod yet.  I've tried using splinter cell and tont hawk pro skater 4 and both do the same thing 

What about the NTSC/PAL console/game region matter? Have checked that too?

Probably done this but make sure the two exploit/installer saves are from a fresh source and not copied in from another Xbox.   

[Problem Softmodding]

What game exploit/installer is being used?

Any chance you accidentally used the Splinter Cell PAL ones when it is NTSC?

Logical follow on from that: are you sure the console is NTSC? It could have been softmodded previously and swapped to PAL for some reason and returned to retail state region changed. With SD cables the NTSC and PAL MS dashes can appear similar at first glance.

There can be some weird things happen if the Xbox has been previously softmodded and you use the same exploitable game with different exploit/installers files. It is possibly caused by leftovers in TDATA although there's never been any real testing to prove/disprove that theory. The solution suggested is to use another exploitable game instead. Any possibility you can try that?   

[Tsop HeXEn Install Questions]

I did my first TSOP (v1.4) last week and used HexIns , the installed version of HeXEn. It was either the 2017 or 2018 update version, not sure.

Maybe useful info: if you use HexIns rather than from the disc for the TSOP the eeprom backup and flash menu Exit Back To Dash EvoX menu option will not function. It is set up to use the path E:\HeXEn Tools\unleashx.xbe which presumes you're using a HeXEn installed C:\ and E:\drive ie. a HeXEn softmod.

Pre-TSOP you might well not be and if you've just installed HexIns from the disc that is going to be wrong too. It can easily be edited to the correct path.

If you use it as is it means that any of the HexIns menu options which launch the EvoX dash, like Lock/Unlock HDD the only way out is to turn off the Xbox. IGR does not work and in any case would take you back to your main dashboard not HexIns. 

AID's equivalent tool, when AID is used installed, has the same issue. The path is back to the D:\drive. That is not so easily edited as the eeprom backup tool is launched from a ZIP folder: eeprom.zip. It needs to re-packed correctly after you've edited the evox.ini path and it seems you can not do that on the Xbox. It needs to be done on the PC.

In answer to the question above:- unless it has been updated recently Slayers IS ancient but the main reason not to use it for a TSOP is that it specifically warns you against using Slayers with softmods. The Xbox is softmodded until it is TSOPed and still has a softmod installation present afterwards. The manual also recommends that you do not try TSOPing at all! Would anyone not confident about TSOPs choose a tool that had warnings like that?

I'm not a fan of any HeXen dash installations either but as a tool set I'd trust it and its built in warnings, explanations and clear instructions 100% for all purposes. It works - you might not like its final finish but once done and the HDD unlocked you can use whatever dashboard installer you want afterwards.

That's what I did: as said I used HexIns for the TSOP BIOS flash. But after unlocking the HDD I simply took it out, put it in USB housing, formatted and  bleached it on PC then back into the Xbox. Cold booted an AID4.53 disc and used it to set up the HDD from new.     

   

[Cannot Load Hexen Cd Anymore After Tsop]

If you use SID/AID discs the start up delay is even greater than HeXEn - typically for me 45 seconds whilst HeXEn is 25 -30 seconds. Even when you install either on the HDD there is a significantly delayed boot.

I think it may be down to the dummy file used to make the discs more readable across the range of disc drives the Xbox uses. But if it is not then I'd be interested to know myself what causes the delay.