| QUOTE (feilox @ Jan 31 2004, 07:42 PM) |
| ok, i'm a n00b, but wat's all this font exploit supposed to do?...i know it's a buffer overun code, but what does it do? does is fool the xbox into thinking that it has a cd? bios?....i need some info |
it does a buffer overrun thatover writes the memory block that stores the ms public key with one of our own, so wel can sign freely
| QUOTE (Grospolina @ Jan 30 2004, 05:06 PM) |
sega27:
You can try any or all of these:
1. Plug in a network cable. Have the other end connected to your PC or a router. 2. Put in an audio CD. 3. Put in a scratched CD. 4. Play with the eject button. Open it or close it when the MS logo appears under the big X. 5. Turn it off and on a few times. 6. Just wait. It may take minutes or hours.
After you get out, be sure to set your clock (EvoX can automatically do it from a time server if you're connected to the net). |
also i heard from someone taht if you turn it on by holding the eject button an dkeep holding it it will boot to evox like every time... well when i had a clock loop yesterday from bringing my xbox to my moms, i did that and it worked great...
btw, thats awesome that you are learning about the fonts

i knew vageuly how they worked but you have clarified a lot of stuff
I just wanted to say my xbox kept on acting really screwy like black scrren red light rebbot ask for time... alot until I gor rid of xodash (the 2.0 version)
Notes I had a mixture of live 2.0 and the exploit dash and was using the audio hack at the time...
| QUOTE |
For all thise who would like to know I tested the 5530 kernal on debug PBL It goes through all the keys from the boot.cfg Goes Calculating 2bl entry point Calling 2bl And hangs |
From this thread
http://forums.xbox-s...ic=175051&st=45So yeah looks like some sort of call is going wrong
we are SUCH dummies! it probly stores the bios in a differnt set of memory blocks.. wait then what about modifying the mpublic key....
| QUOTE (Chicken Scratch Boy @ Feb 29 2004, 06:51 PM) |
| we are SUCH dummies! it probly stores the bios in a differnt set of memory blocks.. wait then what about modifying the mpublic key.... |
what about if it's only initaly storing the bios in another set of blocks and its messing up then it goes to call it so it can inject it/replace the original one in memory?
Grospolina ::: How did you get on with experimenting with the blended fonts, any success in getting out of clock loops?
Dont' know if this will help much, but I have found that everytime I reflash a bios on the Xbox the clock get's reset. If you have a flash enabled bios and a suitable recovery mode (split TSOP/Mod-Chip) in case of bad flash it may help shorten the debug cycle.
I've only used Evox for flashing so I don't know if this is a side effect of flashing the bios or if it's specific to Evox.
gropsplina owns!
COME ON DUDEZ!!!
this is great news gros please keep us posted on your progress with these new fonts your working on dude good job
Easy now Neilor! I don't know what version of the Mech fonts you have, but I would bet you the clock loop is not fixed. I dont see how it could be with the current structure of these fonts. All versions of hacked fonts rely on a somewhat uncontrolable sequence of event to happen in the correct order and therefore no fonts have a complete fix for the clock loop. The success of the fonts rely very much of the environment they run in, and therefore some fonts work well on certain xbox versions but not on others. If you have a set of fonts that work well for you - congrats! But that doesn't mean the loop is fixed. I personaly never had any serious looping with any version of the fonts (reloaded, bigfonts, mech)
Edit : Of course I dont mean to disencourage any further development on the fonts Grospolina. It's just that the 'Clock loop is fixed' posts are numerous on this forum leading some leading some people to go ahead using them without taking precautions, like backing up hd key, eeprom etc.
The fonts in the package contain the feenix version of the hacked mech fonts and even though they don't fix the clock loop entirely they seem to do a pretty good job at it. I modded lots of xboxes of all versions with these fonts and I never experienced a real loop and never had anyone complain that they were in a loop.
These fonts even prevent any upgrades of the dashboard from within a game so in my opinion these fonts are the best ones at the moment'.
Yep. The feenix fonts are the ones closest to the original linux-fonts I think. As I recall they were the ones released by an anonymous hacker who deobfuscated the linux-fonts. Most versions of these fonts are slightly edited to disable the check for linux-specific files (vmlinuz etc.)
is there anyway that you can have it NOT set the clock every time it boots? cause it's kinda annoying habing all your saves be saved at 6-8am on july first, especially when the game loads the lastest one...
ah cool, what else might you have in store for us?
Idots::: looking back at my post it may have been a bit premature to declare the clock loop dead based on the results on my own box only, you are probably right about different versions performing better than others.
But what I can say about these Feenix fonts is that they do appear to be pretty solid on my own configuration, prior to flashing the bios on my XB I had been running Bigfonts for a number of months and managed to get stuck in clock loops on three different occassions, it took alot of messing with network loop-back cables, scratched disks, waiting hours etc.... but I never got out of loops as quickly and as repeatably as i do with these fonts.
Maybe we should pole the newer generation M.I. based exploits and see if there's a pattern (V1.1's might work better than newer XB's???)
It would be most beneficial for a pole if the clock loop can be deliberately induced rather than getting opinions or beliefs that the fonts a person uses don't loop
yep
ah starcraft....
anyway, good luck on the fonting, cxan i beta?
| QUOTE (vintage_guitar @ Mar 21 2004, 11:36 PM) |
Wow, that's the most butchered version of the word "Pheonix" I've seen in a LONG time.
|
I'll take credit for that...
That was done before I understood the fonts, the new version uses the correct spelling of "Phoenix" (Feenix / Debian, both 6 characters)
P.S. Grospolina, I have habibi versions of B&E reloaded and Bigfonts, u r welcome to use them and/or ask again about how to decompress them. (they run from the mechinstaller)
| QUOTE (Grospolina @ Mar 22 2004, 06:19 AM) |
| Thanks for the offer, but I can already make habibi-keyed fonts if I wanted to. I'd rather convert the MI fonts to use the font key instead. |
Ummm, yeah I know u can make your own versions of those fonts. That was more of an offer to teach u how to package them so that they (or your own), can be used in the Mechinstaller.
How is your testing of your hybrid fonts going Grospolina ?
Earlier on this thread you mentioned that you wanted to include code from the Mech fonts in your "Frankenstein" fonts. How about using the "special" exception net of the Mech fonts? Wouldn't you assing most of the "clock-recovering" success of these fonts to this net? The payload of the different fonts more or less have the same goal (though achieved with different means), the important thing being whether we reach the payload or not.
Having fonts with the succes-rate of the Mech fonts, that set the the clock if needed and otherwise boot an application would be sweet!
count me in, i ahve eeprom backups, a spare hdd (stock-efied) and a gs on my hdd... note that i have not have any problems with clock loops with the current fonts (reloaded)
Well i haven't got any sort of backup yet so please don't send me the fonts before i kill my xbox
But I just wanted to say thanks for all the work you have done so far.
I'm not a really active user of xbox-scene but I like to read some text and keep up to date. The only weak points of the Font hack are the speed (they boot up slow
) and the clockloop (the red flashing LED seems to be fixed in PBL 1.41 unofficial) and I hope that you're able to fix this two litle problems that are left.
Thanks and keep up the good work i'm sure the're a lot of people waiting until the clock loop is fixed before the're going to use the fonts hack.
Btw : I hope to have some sort of backup soon so I can test this new fonts they look really really good 
So if the Mechinstaller (Evox) package has a hugely compressed ernie for mem card reasons, its the save game that decompresses it. Is there any way to install it manually without a copy of the game? Or are there decompressed versions floating around?
The bluhdebluhs fonts thread is located here
These first mechinstaller fonts are very close to the linux fonts and I still find these the coolest ones around. Never experiensed loops whatsoever on multiple xbox versions.
Other fonts from catfish's installer can be found at the maxconsole forums. There are several versions around.
I can't really judge since I have not looked into the technical details of the font exploit. Maybe I'll get time in the future to do that. But it seems to me that most people trying to resolve the clock loop the wrong way. Everyone is trying the same basic "solution"; to fix the time.
So why is it impossible to get an executable to load just because the dashboard is trying to load the clock instead of the main dashboard screen? In both cases, it loads the font files. It was my understanding that the fonts caused a buffer overflow to crash the dash. Why is this not happening when it tries to load the clock? It is my guess that it either has to do with the fact that the dashboard refuses to attempt to execute code when the time is not set or it has to do the address jumps become offset when this happens and hence, it doesn't land on the exploit code like it should. I'm sure there's a mathematical solution to the later situation. Any input?
Hi Gros. Sent you a PM with some test results.
If it is posible to load msdash without the original fonts this could work. Don't think
that's possible though.
msdash would be looking for the original fonts (now renamed to .bak).
When msdash is being loaded we have replaced the key in memory, so it doesn't matter that we hexed msdash.
So how is this different than the mechfonts with exception of the hexed msdash? There would still be a possible loop as the fonts need to redirect to the .bak fonts and reload the dashboard?
From the description above when the mechfonts are loaded into memory they patch the msdash that is loaded into memory to look for the original fonts with the new names (*.bak) so in the event that the clock check thread completes before the exploit the time screen can be desplayed. Before if the clock check thread finished first the clock screen would look for the xb *.xtf files it would error screen your a$$.
If in the event the exploit finishes first and the clock does not need to be loaded it mearly loads the ms-dash with what appears to be the link for the xbox live dash pointed to a new locations and since the ms-hash is also modified when you select the dash menu option it loads the program. This set program doesnt need to be say a dashboard it can be an app like dvdx as long as the app is signed with the correct hash key (habibi in this case)
If I am understanding him correctly he is saying to manipulate the ms-dash loaded into memory however far you want to take it
Wooger
From what I understand he wants to let the fonts boot a hexed msdash that uses the .bak fonts. Now since the new msdash needs to be booted from the harddisk wouldn't it take way to much time when the clock is dead and the xbox is desperately seeking for its dash?
. I guess it would only work if launching a new app (msdash.xbe) will kill the thread that will eventually check whether the clock is set or not.
In any case the method that the mechfonts uses to patch dash information in memory is a great idea. Now if you could only manipulate more of the dash such as more tab's other than the "xbox live" tab (which im sure is possible just someone has to take the time to do it) If this can be done the xbox would load its msdash and then things would be manipulated after that so the xbox hasnt the slightest clue its being highjacked.
Do keep in mind though the font exploit is an old exploit and newer exploits really need to be found to work on the newer xbox dash versions otherwise its back to mod chips.
Wooger
P.S. Does anyone get the feeling that the public is testing the M$ software and helping MS fix there problems?
| QUOTE |
| Now since the new msdash needs to be booted from the harddisk wouldn't it take way to much time when the clock is dead and the xbox is desperately seeking for its dash? |
Maybe Grospolina can answer this. When the orginal Mech fonts reload the dash in memory where does it get this dash from. The memory is so sevely messed up from the exploit that it would have to be reread from the harddisk wouldn't it. In that case it's the same situation.
| QUOTE (ldots @ Mar 24 2004, 06:03 PM) |
The current Mech fonts do a lot of patching in memory. What I would hope would be possible was to cut out all this pathing (except the patching of the key), thereby making the exploit more slim in the hope that the exploit would run faster. So this is different from the original Mech fonts in that no in memory patching is needed.
Let me describe again. The original Xbox.xtf and Xbox Book.xtf are renamed to Xbox.bak and Xbox Book.bak. Bert.xtf and Ernie.xtf are present. xboxdash loads bert and ernie. Patches key and launhes msdash.xbe, hexed to look for the *.bak fonts, and to show Phoenix or whatever in the live tab. PBL could then be renamed to xonlinedash.xbe.
Unfortunately I don't think it will work . I guess it would only work if launching a new app (msdash.xbe) will kill the thread that will eventually check whether the clock is set or not. |
Honestly whats the point if the dash in memory is going to look for the original renamed fonts why then would you be concerned if the clock check finishes first. If it does big whoop cause the dash will then load the original fonts and bring up the clock fix screen...
Which is what the mech fonts do...
Wooger
Wooger you misunderstand me. I would not be doing the xtf -> bak patching in memory in this scenario - that's the original Mech exploit! If the xtf -> bak patching is done succesfully there is no point in loading a hexed msdash right!
| QUOTE (ldots @ Mar 24 2004, 06:12 PM) |
| Wooger you misunderstand me. I would not be doing the xtf -> bak patching in memory in this scenario - that's the original Mech exploit! If the xtf -> bak patching is done succesfully there is no point in loading a hexed msdash right! |
Whats the point of changing the original dash to look for its fonts with different names then?
Wooger
| QUOTE (ldots @ Mar 24 2004, 06:12 PM) |
| Wooger you misunderstand me. I would not be doing the xtf -> bak patching in memory in this scenario - that's the original Mech exploit! If the xtf -> bak patching is done succesfully there is no point in loading a hexed msdash right! |
I understand that your saying all you want to do is patch the private key and then from there anything with that key can be run so in the event of a clock loop situation it wouldnt matter the msdash would still function...
Correct?
Wooger
The point would be that if this all worked we would end with public key in memory and a fully booted msdash with a custemized live tab - Just like the original Mech fonts. The only purpose of all this was to cut down on the exploit code in Ernie. But again I dont think this will work.
Would a reloaded msdash end in the same place in memory? If not the "clock thread" wouldn't get to the correct clock setting code of msdash...
Well 5101 kernal here and the one i did last night seems to be stuck in a loop that it's not coming out of with or without a network cable plugged into it.
Hi there Grospolina!
Any news on the hybrid fonts? Any discoveries on if and why the clock-setting code can be kernel dependant?
Installed the 7/25 fonts on K:5101 D:4920
never had a clock loop once. It comes up with the date/time and freezes after a few seconds, then I reboot and it's set to Jan 1 2001 and I'm good to go.
anu|b|iss:
1. these fonts werent around in 7/25
2. read the thread
3. we dont care
4. your sig is too long
And he's posted the same thing on another thread
1. ok, was unaware, always modded with a chip before
2. I had read most of it but skipped to the end to see the current convo (my bad)
3. Nobody said you had to.
4. Fixed that just for you.
5. Neilor, so what?
Any news yet? I'm looking forward to a new version of your Fonts.
Well, I know that this same question has been asked in this same thread, but no one answered. I am running a 5530 kernel and using the bigfonts25 to exploit my xbox. In the begining of your thread you said that the Bert Is Cheating On Ernie fonts patched the kernel to allow F: drive support. Will this also work on my kernal (5530).
A few more questions:
1. How hard is it to splice 2 fonts together?
2. Why do the Mechfonts refuse to work on Kernel 5530?

Also, I'm preoccupied with emulators right now. 
| QUOTE |
At the beginning of the exception code, it first modifies the instruction before it to cause an infinite loop. That way, if another exception is generated, the Xbox will hang instead of trying to run the exploit again.
After step 6 (above), it checks a flag in the data area. If the flag is set, it hangs the Xbox. If not (default), it proceeds. I'm not sure what use this has. |
I'm currently using bigfonts to launch the Phoenix BIOS loader on my box... About one in three times I boot the box, it locks up before the Phoenix logo appears. From the work you've done so far, do you think it's possible to modify bigfonts to remove this lock-up-on-purpose behavior? Or do you think that's even my problem?
All I know is it's pretty annoying to have to reboot the box multiple times...
Thanks!
-Zak
I don't think it's a problem with Bigfonts. I've had this happen with the other font hacks (including my own, which doesn't have the Bigfonts mods). It just seems that it doesn't like to behave all the time. I think it has to do with the Xbox not being reset to the same state all the time, especially after resetting from another program. I just press eject and it usually works.
this is a very good post, thanks alot
Agreed, an excellent post, very informative 
Thanks
yep, very interesting, it may be a good idea to pin it, then maybe more people will add information.
Thanks. I've made some edits to the MechInstaller description. I'll have to actually install it later in order to see how it really works.
Edit: Bah, I can't get it to install.
I've gotten MechInstaller to install, after using a different copy. I've added the information on it to the first post.
Zak0: do you have an old dash with no fonts folder by any chance?
I had my fonts in the C root, and had the exact same problem as the one u described.;; updating with live so that my fonts were in a fonts folder solved that problem for me.
Dont forget to return your box to its virgin state before updating the dash tho
| QUOTE |
| They claim that the clock looping issue is fixed |
If the clock looping issue is really fixed by those font files from MechInstaller. Can we use them to boot Phoenix loader? The only thing we need right now is a highly reliable clock looping fix, isn't it?
| QUOTE |
| If the clock looping issue is really fixed by those font files from MechInstaller. Can we use them to boot Phoenix loader? The only thing we need right now is a highly reliable clock looping fix, isn't it? |
true, but apparently they've made the code really hard to debug (for the purposes of keeping non-Linux users from using it). People are trying to break it down now, but it's proving difficult.