Search for a better clock solution

[underthebridge]

OK so we know the load sequence goes like this:

xboxdash.xbe --> bert + ernie.xtf --> default.xbe

Now when the clock dies, the bios demands xboxdash.xbe no matter what. If any xbe other than xboxdash.xbe is run afterwards, the bios will try to load xboxdash.xbe and this is what is causing endless reboot cycle, correct?

So far it has been proven unreliable for hacked font files to actually SET the clock, or DETECT the invalid clock (which one?).
My proposition: What you could do is modify bert and ernie so that when an invalid clock is found, they patch the kernel in memory with a different filename of the default xboxdash.xbe, then load that instead.

1) Clock dies

2) Bert and ernie detect dead clock and patch xboxdash.xbe with msdash.xbe in bios kernel. The fonts also now change their path from default.xbe to msdash.xbe. If the difficulty resides in actually detecting the dead clock, you can use some form of manual user input (eject tray).

3) msdash.xbe can now be loaded without interference from the bios. This can be an ms dashboard, hacked so that it points to XFT fonts, font-signed with xbedump.

I have verified that loading an xft-hacked, font-signed ms dashboard directly with bert and ernie CAN set the clock.

I am pretty sure something like this will work. If only I had the skills to code it... :(
Your thoughts o phoenix masters ;)

[ionic]

Sorry to disappoint you, but that is not the problem.

The bigfonts already correctly set the clock.
The resetloop is because the box crashs before
the exploit code gets active.

[underthebridge]

well it was worth a shot...
May I ask you what specifically causes the crash?

[underthebridge]

Is there no way that we can find a 100% working solution to the damned clock problem? If if it's just theoretical for the moment, there HAS to be some way. I mean, I really wish we could put this thing in the past...

[AlcoholFuelled]

As or right now there is NO fix for the clock problem. I know every noob that has ever spoken to someone who knows someone who is related to a guy that has a sure fire method of avioding the boot loop with the Phoenix Loader but I will tell yuo right now NO. No there is not a solution, yet. There could very well be one in the future but who can really say when.


Cheers
AlcoholFuelled

[keystroke]

I've not yet had the loop-problem on my 1.0 box, but others I know have had the problem and solved it first time each time by plugging an ethernet cable into the X-Box and linking it to the PC.

Not sure whether this will work with everyones setup but it has worked with a few people I know using direct crossover cable (xbox > pc with no router)