Print

[skorchir]

Sorry But I Believe This deserves its own space

I will keep adding any findings i come by

-------------------------------------------------------------------------------
well i got progress in getting my boot order working great
i got my boot sequence as follows

d:boot.xbe
c:avalaunch.xbe
c:evoxdash.xbe
c:mxmdash.xbe
c:nexgen.xbe
c:xboxdash.xbe

there seems to be 5 boot options for dashboards i tested it and it boots all in that order. anyway what i did to extend my dash names was simply borrow bits. for each bit removed a bit is inserted. for each bit longer a bit was borrowed from a not used or inserted bit.

i opened Hex Work Shop 4.2 loaded xboxkrnl.img

went to Edit, Find and searched for 'evox' All Instances, ASCII String.

and it showed two sections containing that string
the first one was under X3MAGIC so i fixed it to my liking

borrowing and supplimenting at the end of each xbe name bits '00'. After some customizing i went to the second instance which contained actual boot locations in visable text.

CdRom0boot.xbe...DeviceHarddisk0Partition2avalaunch.xbe

well again i changed what i needed. borrowed bits. in this part i borrowed some bits from cdrom. i used boot.xbe oppsed to default.xbe

apparantly the only thing that works in this part is the Cdrom boot xbe. ive changed it and it works but it seems the rest of the hard drive partition and xbe names are overwritten by x3magic. this is not totally confirmed. I can confirm the cdrom boot xbe remains working.

saved my kernel packed it with xbtool v1.0.12, flashed with evox and all is good works to my expectations

This part here is taken from the other thread written by 82ross adding it to keep all information in one post

QUOTE

TUTORIAL FOR X2 4980 DASHBOARDS ON A DIFFERENT PARTITION Software needed: XBtool Any hex editor (UltraEdit32 is used in this example) 1) Start XBtool. 2) In the "Bios Type" drop down box make sure it says "Multi". 3) Click unpack. 4) Locate and selesct the 4980 bios of your choice and click "Open". 5) Minimize XBtool and goto the folder where your bios was located you should see a folder with the same name as your bios. Enter this folder. You should see 3 files. 2bl.img remainder.img xboxkrnl.img 6) Open up xboxkrnl.img in your HexEditor. 7) In your hexeditor find the Goto function. In UltraEdit32 its "Search>Goto Line/Page" (Ctrl+G) In the box that pops up enter the address 0x2d154. 9) This should jump to that location. In UltraEdit32 it should look like this: 0002d150h: 00 01 00 00 02 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash The first section befiore the : is the address The 16 pairs of numbers after that is the hexcode After the ; is the ASCII version of the hex code. 10) The number in bold is the code we are interested in (0x2d154). 02 means partition2 11) Click on the 2 in the 02 and press: 1 to boot dashboards from partition E: 0002d150h: 00 01 00 00 01 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash 6 to boot dashboards from partition F: 0002d150h: 00 01 00 00 06 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash 7 to boot dashboards from partition G: 0002d150h: 00 01 00 00 07 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash 12) Close and save this file. 13) Go back to XBtool making sure Multi is still selected. 14) Click on the "Pack" button. 15) Select the xboxkrnl.img you have just edited. 16) A Save As dialog pops up. Enter the name you wish the bios to be called. 17) Your new bios will be in the same folder as your xboxkrnl.img. 18) Flash your modchip with this new bios. Following on from 0x2d154 you can see the names of the four dashboards in the order they will be loaded. You can rename these if you wish. I would keep the length of the names the same. Only overwrite current names. Do not extend the names as this maight break the bios. This will probably change in the future.

if you attempt this BE CAREFUL not to borrow anything not 00 and where you borrowed it from.

-------- TRADE MARK SYMBOL --------

To Remove The 'TM' symbol from the boot simply goto location
00060968 and change hex values 18 to 20

you can also do a hex search for 455c c1e0 1889 and change the 18 to 20

----------- X COLORS ------------

you can get your hex colors by takeing the red,green and blue custom numbers and using the windows calculator in scientific mode and enter the number in decimal and click hex to convert to hex.

X Lip

HEX Offset: [0x0002D1A8]

was 00 01 00

X Lip HighLights

HEX Offset: [0x0002D1AC]

was 4B 9B 4B i changed it to FF 00 00 for a blue color
In here it goes backward BLUE GREEN RED (when doing custom colors) so FF = 255 Blue 00 green 00 red

X Inner Walls

HEX Offset: [0x0002D1B0]

was 17 6A 21

X Inner Glow

HEX Offset: [0x0002D1B4]

Was 01 DF CB

XBOX Text

HEX Offset: [0x0002D1B8]

was 13 CA 62 i canged to DA 65 17 for another custom blue text.

ALL TESTED AND WORKS PERFECT!

WOOT!

---------- SPLASH LOGO ------------

HEX Offset: [0x0005A81C]

was 75 0B to disable change to 90 90

---------- NO ANIMATION -------------

HEX Offset:
[0x0005B222]
was 74 09 now 90 90

[0x0005B989]
was 74 09 now 90 90

[0x0005C083]
was 75 0EE9 979D now E9 0B00 0000

[0x0005C0AB]
was 75 05E8 A99D now E9 0200 0000

---------- X LOGO ----------------

To remove this

[0x0005B56C]

was E8A7 F7FF FF now 9090 9090 90

[0x0005C06D]

was E8 5AF3 FFFF now 90 9090 9090

also add

[0x0005B222]
was 74 09 now 90 90

[0x0005B989]
was 74 09 now 90 90

[0x0005C083]
was 75 0EE9 979D now E9 0B00 0000

[0x0005C0AB]
was 75 05E8 A99D now E9 0200 0000

------------------------------------------------------------------------------

I sure hope NghtShd updates xbtool it was a very useful tool and probly one of the most needed app for the xbox. dont want to see a good program go out of production  
Hopefully he can use this info to update XBTool or someone else can possibly make a small patcher for this!

I will see what else i can find but a lot of the work is already found for you

Once Again Unless You Can Recover From a Bad Flash Or Improper Editing USE AT OWN RISK. I TAKE NO RESPONSIBILITY!

Enjoy Happy Hacking  B)

This post has been edited by skorchir on Jan 14 2004, 04:02 AM

[Xbox-Savage]

amazing!!    nice

[dzv]

Great work, but I still can't get it to boot from F: first.  I had already tried to do this before, by changing the first boot location from

CODE

\Device\Harddisk0\Partition2\evoXdash.xbe

to

CODE

\Device\Harddisk0\Partition6\evoXdash.xbe

However, this didn't make any difference, it still booted to C:\EvoXdash.xbe first

It seems that the first section of boot locations (something called X3 Magic) over-rides the other settings.  The problem is, this 'X3 Magic' thingy doesn't allow you to specify the partition, only the filename.

Anybody had any luck with getting it to boot from F: ?

This post has been edited by dzv on Jan 11 2004, 01:37 PM

[82ross]

The string locations for the dashbards do not make any difference anymore.

You can change replace all the other strings with 00's and it will make any difference. They are useless. Dont bother changing the string from partition2 to 6 your wasting your time.

Goodjob skorchir. Youve found most things people have requested. It deserves its own thread.

EDIT:
Thanks man

This post has been edited by 82ross on Jan 11 2004, 05:30 PM

[skorchir]

QUOTE

The only one im not sure about is the cdrom one, i havent tested that.

yup this one works ive changed and tested it  

[skorchir]

BTW Think This Thread can be pinned? or at least till someone makes a patcher tool

Also if anyone knows of anytools that will dissassemble the xboxkrnl.img file into C or any other interpretable language so i can get a closer look and possible re-assemble please let me know.

---Another Discovery---

well i noticed that the new kernel was significantly smaller then their previous ones.. after a bit of poking around i discovered that at the end of their previous kernel 4979 there is a part "Kernel Expansion" which contained the front LED and Fan Speed Offsets. It seems this was removed from the 4980 kernel. What i tried was copying and insertting this section into the new kernel, changed some values, packed it and flashed it to my xbox but didnt see any change same boot up no led change nor fan speed increase.

What can this mean? Well either its been removed from their kernel totally ? or its been moved and simplified in the code.

Il keep messing around to see what i can find.. im actually enjoying this

anyone is welcome to support this thread with any help, guidance or information.

This post has been edited by skorchir on Jan 11 2004, 08:24 PM

[NghtShd]

QUOTE

---Another Discovery--- well i noticed that the new kernel was significantly smaller then their previous ones.. after a bit of poking around i discovered that at the end of their previous kernel 4979 there is a part "Kernel Expansion" which contained the front LED and Fan Speed Offsets. It seems this was removed from the 4980 kernel. What i tried was copying and insertting this section into the new kernel, changed some values, packed it and flashed it to my xbox but didnt see any change same boot up no led change nor fan speed increase. What can this mean? Well either its been removed from their kernel totally ? or its been moved and simplified in the code.

I think you're referring to my XBtool kernel additions. Were you looking at a kernel which had been previously patched using XBtool?

I add my own dashboard loading function (mostly copied from one of the X2 kernels, as I recall, so I probably shouldn't refer to it as my own) and I put my LED color and fan speed setting calls there. It sounds like that's what you're referring to. There's a total of 32k added on to a stock BIOS, though most of it is just slack space, the rest being LBA48 code (where applicable), the dashloader/LED/fan functions, and some code for keeping the expanded kernel code from getting deleted.

[nuzzy]

if you can find how to get the fan mod to 100% that would be great!

[skorchir]

Ah yes you are correct i examined a unedited kernel and it was not there you are right

i was reading a unedited kernel but i did save it with XBTool as i was comparing differences between other modified kernel images and thus comparing similaraties to the 4980 kernel this is how i was able to find the kernel hacks within the new kernel.

Im hopeing you can take the information found and update parts of xbtool even if it doesnt do everything just the simple patches already found it makes things easier for people.

 

[Heykrop]

QUOTE (dzv @ Jan 11 2004, 12:35 PM)

Great work, but I still can't get it to boot from F: first.  I had already tried to do this before, by changing the first boot location from CODE DeviceHarddisk0Partition2evoXdash.xbe to CODE DeviceHarddisk0Partition6evoXdash.xbe However, this didn't make any difference, it still booted to C:EvoXdash.xbe first It seems that the first section of boot locations (something called X3 Magic) over-rides the other settings.  The problem is, this 'X3 Magic' thingy doesn't allow you to specify the partition, only the filename. Anybody had any luck with getting it to boot from F: ?

 Yes I did.  I followed the instructions that were originally posted by 82ross and are quoted in the first post of this thread.   I simply changed the 02 value at offset 0x2d154 to a 06.  Saved the file and then repacked with XBTOOL.  
 All my dashboards are on F: and it booted fine. I may now go back and try the bit borrowing procedure to see if I can get it to boot unleashx.xbe on F:   I tried it last night by only renaming a dashboard item in the X3Magic section of the bios and by adding the extra character it caused an error 13 when trying to boot to that item.

I'm aslo going to try the color offset changes as well as the TM removal.

[82ross]

What extra character? Just type over evoxdash with unleashx (under the x3 magic part only), they are both 8 characters long so it shouldnt be a problem. If you wanna type over the other 3 locations just shorten the name of your dashboard xbe to7 or 6 characters accordingly.

This post has been edited by 82ross on Jan 12 2004, 08:59 AM

[Pathetic]

QUOTE (skorchir @ Jan 11 2004, 09:41 AM)

---------- NO ANIMATION ------------- HEX Offset: [0x0005B222] was 74 09 now 90 90 [0x0005B989] was 74 09 now 90 90 This removed the startup animation. Side Effect: On Power Up Animation was removed successfully but the sound plays for 1/10th of a second very minor and stops. can't even hear or notice it unless you know its there This still could be potentially dangerous.

 Does this mean it hangs, won't boot ?
I want to diable animation but im not shure to try this

[Heykrop]

QUOTE (82ross @ Jan 12 2004, 07:55 AM)

What extra character? Just type over evoxdash with unleashx (under the x3 magic part only), they are both 8 characters long so it shouldnt be a problem. If you wanna type over the other 3 locations just shorten the name of your dashboard xbe to7 or 6 characters accordingly.

Thanks for that info.  I was aware of that.  I usually have 2 or 3 dashboards on the drive as a failsafe incase EvoX or another fails.   I generally leave EvoX as my default dash so I can manage Chameleon functions.  I have links in all of them to each of the others.  This was my method of staving off the system booting to the M$ dash if EvoX failed for one reason or another.    

So I could have changed evoxdash.xbe to unleashx.xbe but then EvoX would not be the default.   I wanted to replace mxmdash.xbe or nexgen.xbe with unleashx.xbe and that did not work.      

[skorchir]

QUOTE (Pathetic @ Jan 12 2004, 06:12 AM)

Does this mean it hangs, won't boot ? I want to diable animation but im not shure to try this

 
No this actually worked it removed the animation and booted the system there was just a short play of sound on power on it plays for 1/10th of a second hardly noticable. but like i said dont use or try this unless you are able to recover from it
good luck

[skorchir]

QUOTE (Heykrop @ Jan 12 2004, 08:55 AM)

So I could have changed evoxdash.xbe to unleashx.xbe but then EvoX would not be the default.   I wanted to replace mxmdash.xbe or nexgen.xbe with unleashx.xbe and that did not work.

you can change evoxdash.xbe to unleashx.xbe to make unleashx your primary dash. now you can overwrite nexgen.xbe or mxmdash.xbe with evoxdash.xbe and steal a bit from another one of the xbe names

this is what my X3 Magic section looks like and it works like a chram

CODE

****X3MAGIC!****........avalaunch.xbe...evoxdash.xbe....mxmdash.xbe.....neXgen.xbe......xboxdash.xbe............

this is what it originally was.

CODE

****X3MAGIC!****........evoXdash.xbe....avadash.xbe.....mxmdash.xbe.....neXgen.xbe......msxboxdash.xbe...

i renamed msxboxdash to xboxdash. this gave me 2 bits to play with. this is actually all i needed. For your situation it looks like you only need to steal 1 bit so remember to add any unused bits back to the end of the xbe name from which you took it from. unused bit should be added as 00. i hope this helps you. good luck

This post has been edited by skorchir on Jan 12 2004, 05:27 PM