A xellous dumped "config_raw.bin" and ibuild.exe "smc_config.bin" question

[madusmacus]

I just hacked a config_raw.bin into smc_config.bin by...

Deleting 0x4200 bytes off the front of the config_raw.bin and
Padding it out to the same size as a smc_config.bin with 0xFF's

although they HexCompare nicely the question is...

Have i made a real smc_config.bin that ibuild.exe can use to make freeboot0.32 image
or is there some fundemental flaw in my idea?

Many thanks for reading this

P.S. I have my reasons for doing this and i know about all the tools etc :¬)
P.P.S sorry if i have chosen the wrong place to post this

[soulwarrior]

Using hexworkshop you could done it this way also:
1. open rawconfig.bin <--- rawconfig from nandpro not config.bin from flash tool
2. goto offset 00004200
3. Edit --> select block ---> Method size of block ---> 4000
4. Copy the highlighted portion to a new file and name it smc_config.bin

The problem is, is that i don't know if rawconfig files are the same size regardless of the motherboard, and i don't know if the offsets are the same. This has only been tested with a falcon.

[madusmacus]

Hi thanks for the info

Im primarily interested if you can trust xellous dumped config_raw.bin
and convert it into a smc_config.bin as i tried to do.
after i did my hack i checked agains a donor jasper512 smc_config.bin and
i had more info in my one than the donor one that was created with ibuild.exe



I had to use the xellous dumped config_raw.bin because...
I have Jasper512 Xbr3 images here alot of tools currently dont like this

1) config.bin from flash tool 0.93 currently just dumps an empty file
    probaly a Jasper512 issue again offsets
    I know 0.94 is going to be excelent for confid blocks though :¬)

2) I think i can get the config blocks using nandtool using
    nandpro.exe dmp_large_1.bin: -r512 SMC_config.bin ef8 8 :AA3020
    note the ":AA3020" is the only way to get it to read xbr3 jasper512 images
    and the size is to big have to use hexworkshop to trim it.
    this is all to heavy on my brain

So if anyone knows if i can trust what i did please let me know :¬)

Many thanks

[foouser]

I just compared my files (got config_raw.bin and smc_config.bin from the same console), and pretty much found what needs replacing.
Take the donor smc_config.bin file, and fill in your unique data by copying it from the config_raw.bin file. I'm not 100% sure it's correct, but I only found 3 specific areas that needs changing (rest is FF padding).

Copy the contents from the range of 0x4200-0x422E (including 0x4200 and 0x422E) from your config_raw.bin to the range of 0x0-0x2E in your smc_config.bin file. Do the same for the next ranges: 0x4218-0x4228 from config_raw.bin to 0xF2-0x102 in smc_config.bin, 0x4410-0x460F from config_raw.bin to 0x200-0x3FF in smc_config.bin


That's pretty much it. You can try and report. Hope someone will create a tool in order to automate this process.

[madusmacus]

Foouser, thanks for info looks good but...

 i cant test becasue im seeing other differences between my config_raw.bin and donor sm_config.bin :¬(

File "config_raw.bin" of jasper 512 UK xbr3 image - made with xellous http server
Shows blocks of FFDF01000000000000000000402DA8C2 as im my jpg abouve

repeated at :-

0x00004820   
0x00004A30
0x00004C40
0x00004E50   
0x00005060   
0x00005270   

that are not in the donor smc_config.bin :¬( just FFFFFFFF's
maybe this is a xellous dump thing or my xbr3 was BAD in some way :¬(

does this hex patern mean anything to any one?

[foouser]

OK, I created a small utility in order to ease things a-bit. You can try it, and it's based only on my experience with my own personal files. USE WITH CAUTION.
Download: http://www.multiupload.com/H7BC3ZSKEP

Also, of course the donor file and the config_raw.bin file you got is different, it includes a larger sample of data which isn't needed for the smc_config.bin file. Since it's only a file created by ibuild in the process of making a freeBOOT image, some people could not get their smc_config.bin file because they don't have the full dump. Using this utility will help them create a customized freeBOOT image, since using smc_config.bin file from a donor NAND will result in your Xbox using configurations which are not 100% compatible with it (plus, maybe a lost MAC address, calibration data, etc).

[madusmacus]

Foouser thanks for writing all that :¬)

The reason i started all this in the 1st place was because...
using donor smc_congif.bins has made my xbox360's report all kinds of unreal cpu/gp/... temperatures
This is because of gains and offsets are from the wrong (donor) motherbord etc i belive
also i cant have my 2 boxes having same mac addresses on this same subnet

It looks like ibuild.exe makes 128k byte smc_config.bin's
and i dunno how much of it is realy needed when using ibuild.exe to rebuild the freeboot image

So I still need to clear up whats going on in config_raw.bin with my repeating blocks of hex (as above)
So personaly im gonna wait till i can clear up my worries

Many thanks :¬)

P.S. http://www.xboxhacker.org/index.php?topic=13009.40    
reply #55 looks promising

[foouser]

Have you tried the tool? It should build an smc_config.bin file from your config_raw.bin file. After reading about the problems you're having with the donor file, I believe it might be worth a try.

[madusmacus]

Have you tried the tool? It should build an smc_config.bin file from your config_raw.bin file. After reading about the problems you're having with the donor file, I believe it might be worth a try.

Hi ya :¬) Thanks for the proggy :¬)

I gave it a go and like so many tools because i have a Jasper512 things go pear shaped
Dam these 512's dam them all to hell hehehe

ibuild.exe blaahh blahhh blahhh
ERROR: File "smc_config.bin" has a size of 16384 bytes. Expected size is 131072 bytes.

I know i could just manualy pad this with FF to 128k but it defeats my point of this thread :¬(
i have things in that 128k space that i have no idea what or if they are needed
ya know the repeating paterns of hex
FFDF01000000000000000000402DA8C2
as im my jpg image above in this thread

If anyone knows what this prepeating patern is please lemme know
its doing my head in :¬)

P.S. im startign to think its crap in my xbr3 when it was made

[foouser]

Could you please have your donor PM me his config_raw.bin and smc_config.bin? I'll look into that, since obviously RAW2SMC expects a 33kb file and outputs a 16kb file. BB Jaspers have a different-sized config block, which I of course forgot about completely.

[madusmacus]

Could you please have your donor PM me his config_raw.bin and smc_config.bin? I'll look into that, since obviously RAW2SMC expects a 33kb file and outputs a 16kb file. BB Jaspers have a different-sized config block, which I of course forgot about completely.

Thank you alot for taking interest in my problem
I have PMed you the usrl to get the files requested

Many thanks

[foouser]

After a quick inspection, I found out that the only difference between the BB smc_config.bin and the small-block one is the padding. The BB of course has a-lot more padding in the end of the file, but the unique data is taken from and put into the same places both in the config_raw.bin file and in the smc_config.bin file.

Here's a version of RAW2SMC that should create a proper-sized smc_config.bin for BB Jaspers (note that your config_raw.bin file must be exactly 33kb in size), and please read the ReadMe file:
http://www.multiupload.com/H9VVPQ3MLH

[madusmacus]

Firstly many thanks again for your help and interest :¬) but...

Once again i beg to differ there is substantial differences
as mentioned before all the repetitious hex string of
FFDF01000000000000000000402DA8C2
at many oplaces in the file (locations are above too)

I use HexCmp.exe to compare the two and you can clearly see difference
ill post another image here....



also chop the 1st 4200 off of config_raw.bin before tryign to compare or they are all out of sync
you can clearly see differences even at offset 0x0

Thanks for taking time to look into this with me but im still no nearer to understanding these differences :¬(

[madusmacus]

actualy Foouser - i think your right
None of this matters a dam :¬(

as long as ALL the relevant info is moved to the donor smc_config.bin who gives a monkey
I got way to bogged down in WHY!

thanks for all your help

Edited: what i typed here was rubiish i am sorry
should have read
as long as ALL the relevant info is moved from the xellous dumped config.raw.bin who gives a monkey
i am realy sorry for that

[foouser]

Man, I think you got it all wrong. The config_raw.bin file you have is the file that includes your own PER-CONSOLE information. The so-called 'donor' smc_config.bin file has information from a different console. All I did in my utility is to create your own smc_config.bin with the config_raw.bin file you provided. Of course there will be differences! The data in the smc_config.bin created by the tool is using the information taken from your config_raw.bin, and the donor smc_config.bin has information out of config_raw.bin from a different console.

If you'll run the tool on your own config_raw.bin file, you'll get the smc_config.bin file needed. Just use it in ibuild, and you should be good to go (your problems should go away).

[madusmacus]

Hi ya again :¬)

All through this thread I was interested why there is mega differences between the Xellous config_raw.bin and donor smc_config.bin
Not the obvious ones like fans stuff and mac address stuff but the stuff i showed in my images

Its all academic - i was worried because i was goign to write exacly the same thing you did and i needed to know what was important

your program nicely transfer the bits it deems important of the Xellous dumped "config_raw.bin" to a ibuild.exe compatible "smc_config.bin"

This is loverly :¬):¬) and i thank you
as long as all the important info is transfered it is a god send
I was just being cautious but i have lost the will to live now hehehe :¬)

I ran your program on my TWO xboxes and Just for fun here is a 3 way comparison

I thank you once more and Im done here :¬)

[TheBiGW]

So I just flashed my Jasper512 using this tool to convert my config_raw and it worked a treat! Thanks man.