Print

[boflc]

CODE

smc-comparison-tool v0.2
-----------------
thank you, scene.
-----------------
usage: smc-comparison-tool
     : --image1=[nand image 1]
     : --image2=[nand image 2]

. compares the SMCs between two images if both above are provided
. lists the SMC details of a single image if only one is provided
. allows changes to be made to either SMC

http://www.megaupload.com/?d=223XNYPT

consider using this tool when flashing a new image to your box; specifically, i've heard of [and dealt with] too many ppl trusting their favorite fbbuild wrapper and ending up with an SMC that doesn't match their wiring.

this is a command-line application, so you will need to drop to DOS.

e.g., assuming you wanted to compare a xellous/Flash360 dump (flashdmp.bin) with an fbbuild-created (or fbbuild-wrapper-created) image (updflash.bin), you would run:

CODE

smc-comparison-tool-0.2 --image1=flashdmp.bin --image2=updflash.bin

e.g. if you just want to see how your system is wired, grab a xellous/Flash360 dump (flashdmp.bin)

CODE

smc-comparison-tool-0.2 --image1=flashdmp.bin

further, the tool will allow you to change either image's SMC's JTAG TDI & TMS source locations in case you want to switch wiring... or.. i don't know, change an fbbuild-wrapper's improper SMC.

oh, and yes, i know, i threw in crappy CF/CG interpretation and it won't always be correct (ie, i'm just grabbing the values from the 2 patch slots and calling one of them CF and the other CG).


edit: not to be used with Xenon's nor Cygnos installations.  at the core, this is just a wrapper for blackaddr's smc_util (thanks!)

This post has been edited by boflc: Aug 2 2011, 01:25 AM

[rigger66]

Just would like to add, that this app is a must for all who plan to update their  freeBOOTS.

This will hopefully save a lot of peeps a trip to their local flasher, (from a bad flash)

Thank you bolfc for your time and efforts.  (IMG:style_emoticons/default/smile.gif)

Regards

Rigger66

This post has been edited by rigger66: Aug 2 2011, 03:15 PM

[boflc]

CODE

$ ./smc-comparison-tool-v0.3.exe; #cygwin, not 'nix :/
smc-comparison-tool-v0.3
-----------------
thank you, scene.
-----------------
usage: smc-comparison-tool-v0.3
     : --image1=[nand image 1]
     : --image2=[nand image 2]
     : --compareOnly

. compares the SMCs between two images if both above are provided
. lists the SMC details of a single image if only one is provided
. allows changes to be made to either SMC

. --compareOnly can be used if you are not interested in making changes

http://www.megaupload.com/?d=MG51P2HU

consider using this tool when flashing a new image to your box; specifically, i've heard of [and dealt with] too many ppl trusting their favorite fbbuild wrapper and ending up with an SMC that doesn't match their wiring.

this is a command-line application, so you will need to drop to DOS.

e.g., assuming you wanted to compare a xellous/Flash360 dump (flashdmp.bin) with an fbbuild-created (or fbbuild-wrapper-created) image (updflash.bin), you would run:

CODE

smc-comparison-tool-0.2 --image1=flashdmp.bin --image2=updflash.bin

e.g. if you just want to see how your system is wired, grab a xellous/Flash360 dump (flashdmp.bin)

CODE

smc-comparison-tool-0.2 --image1=flashdmp.bin

further, the tool will allow you to change either image's SMC's JTAG TDI & TMS source locations in case you want to switch wiring... or.. i don't know, change an fbbuild-wrapper's improper SMC.

oh, and yes, i know, i threw in crappy CF/CG interpretation and it won't always be correct (ie, i'm just grabbing the values from the 2 patch slots and calling one of them CF and the other CG).


edit: not to be used with Xenon's nor Cygnos installations.  at the core, this is just a wrapper for blackaddr's smc_util (thanks!)

[Midnight Tboy]

hiya,

As mentioned on the Easy Freeboot thread, I've just ran your little app so I can see the method the guy used to mod my jasper

smc-comparison-tool-0.2 --image1=freeboot.bin

(this was using the freeboot image on the cd given by the guy that jtagged my jasper - I haven't yet ran to make a new flash dump on my 360 itself based on current setup since dashlaunch updates etc)

My results are

       file:             freeboot.bin | freeboot.bin
         CB:                     6723 | 6723
         CF:                     4532 | 4532
         CG:                    12611 | 12611
hacked SMC?:                        1 | 1
        TMS:               ARGON_DATA | ARGON_DATA
        TDI:                    DB1F1 | DB1F1
    PCI Bug:          found at 0x2E9C | found at 0x2E9C

Would I be right in thinking that the bit I need to look at is ARGON_DATA?  So this would imply the standard method was used?

[boflc]

Yes, you have the old "standard" wiring for non-xenons.

Go ahead and create your new image and then run the comparison on your source and the new image; more than likely it'll be good to go as most tools don't screw standard smc's up.  Always better to be safe and manually check afterwards, tho.

[boflc]

was just alerted that megaupload is down (thanks johndoe888), so here's an alternate link:

http://www.fileserve...n-tool-v0.3.rar