Tweaking SMC Config Values to obtain lower temps (CPU/GPU gain, offset, etc)

[nicnull]

when editing the config, do not use the saved dump. Extract it's smc_config file using flashtool and put on the rebooter build files. Build the rebooter again with the new edited smc_config.

It's possible to flash only the edited config block if you have the 360 rigged to the PC instead of flashing the whole rebooter again:

nandpro lpt: -W16 smc_config.bin 3DF 1

Or else...?

So thats why the usb stopped working in Xell?
I'll better try the correct way instead.

Could I just extract the smc config block from the saved modified flash dump tool file and then just flash that?

Code:

nandpro fanmod.bin: -R16 smc_config.bin 3DF 1
nandpro lpt: -W16 smc_config.bin 3DF 1

Or is the problem that flash dump tool is doing something else wrong?

I have flashed the saved dump and the system appear to work, not counting the usb in xell part.

[bluespace77]

So thats why the usb stopped working in Xell?
I'll better try the correct way instead.

Xellous only detects USB drives from a cold boot. Remove the power cord, insert the USB device and then power on.

[canderousa]

when editing the config, do not use the saved dump. Extract it's smc_config file using flashtool and put on the rebooter build files. Build the rebooter again with the new edited smc_config.

It's possible to flash only the edited config block if you have the 360 rigged to the PC instead of flashing the whole rebooter again:

nandpro lpt: -W16 smc_config.bin 3DF 1

If I someone doesn't have nandpro access (or it's a pain in the butt to open up the console, etc), then the fastest way to do it is to edit the dump via 360 Flash Tool and re-flash the NAND, is that right?

[l_oliveira]

If I someone doesn't have nandpro access (or it's a pain in the butt to open up the console, etc), then the fastest way to do it is to edit the dump via 360 Flash Tool and re-flash the NAND, is that right?

You will brick the console if you do that.  That's why I said to rebuild the image with the new config block on the rebooter.

[bluespace77]

Hasn't bricked mine...

I assumed it was perfectly safe to do it in that manner, as the fanspeed patcher worked fine for me too.

[canderousa]

If I someone doesn't have nandpro access (or it's a pain in the butt to open up the console, etc), then the fastest way to do it is to edit the dump via 360 Flash Tool and re-flash the NAND, is that right?

You will brick the console if you do that.  That's why I said to rebuild the image with the new config block on the rebooter.

Yea...if you check my 1st post in this thread, I edited the heck out of my SMC_Config via 360 flash tool (all the offset, gain values) because my donor nand used incorrect values. That didn't brick my console...so why would editing temp values brick it??? I thought 360 Flash Tool was meant for this. Here's my procedure:

-Dump NAND blocks (first 66MB) via Flash 360 application
-Open NAND in 360 Flash Tool v0.97
-I go to TOOLS>>>EDIT CONFIG (then click on "Edit Config Button" on the bottom left to UN-grey my settings)
-edit my settings as needed
-Hit the "Save Config" button and enter file name updflash.bin
-update my NAND with the newly created file via Flash 360

You're a smart guy l_oliveira! This should be easy for you

[l_oliveira]

The problem is that up to a certain version of the flashtool if you opened a image and then saved it would modify some stuff that would break the rebooter.

I don't know if that got changed. You know the wording "better safe then sorry".

And it's a pain in the b*tt open a console to flash through SPI if you can flash it in simpler ways.

[canderousa]

I definately agree with "better safe than sorry".

What other safe/easy way(s) can I flash my console? Opening the console and soldering a flasher is not exactly quick.

Is there a way to inject a modified smc_config.bin into a working NAND image? I would then flash it via Flash 360.

Thanks.

[efegue]

EDIT: nevermind, found it!

[l_oliveira]

what about the cpu? Is it possible to force it to maintain X temperature?

It's possible, yes. But keep in mind that only XENON has independent speed control for each fan.
On all HDMI consoles only one PWM (speed control) exists for both fans.

EDIT: nevermind, found it!

How silly of you edit your own message ... 
It was a good question...

[canderousa]

Is there a way to inject a modified smc_config.bin into a working NAND image? I would then flash it via Flash 360.

Anyone? Sorry if my question is dumb. I think the answer is it's impossible...

[pkmz]

Did the recommended settings and everything runs amazing. My temps are in the 50's on all of them. Thanks everyone.

[canderousa]

Did the recommended settings and everything runs amazing. My temps are in the 50's on all of them. Thanks everyone.

Glad that worked out!

Did you flash via nandpro + SPI or thru 360 Flash tool and Flash 360?

[l_oliveira]

Is there a way to inject a modified smc_config.bin into a working NAND image? I would then flash it via Flash 360.

With nandpro and files on your HDD:

You can either move the config block from a image file to another or you can simply flash it straight to the console if it's hooked to the PC through SPI.


To dump the smc_config from a flash image:

nandpro file.bin: -R16 smc_config.bin 3DF 1

To write smc_configbin into a flash image:

nandpro file.bin: -W16 smc_config.bin 3DF 1

(Please OBSERVE that R and W commands are in uppercase.)

To dump the smc_config from a console through SPI:

nandpro LPT: -R16 smc_config.bin 3DF 1
nandpro USB: -R16 smc_config.bin 3DF 1

To write smc_configbin into a console through SPI:

nandpro LPT: -W16 smc_config.bin 3DF 1
nandpro USB: -W16 smc_config.bin 3DF 1

[pkmz]

Neither. I actually broke my console not reading the read me in blackaddr smc config program =\

So I rebuilt the image and had to reflash.

[canderousa]

Sweet! Thanks l_oliveira.

This will be my method since I don't have an SPI flasher hooked up to my console/PC:

-Dump NAND blocks via Flash 360 application
-Open NAND in 360 Flash Tool
-Edit my settings as needed
-Hit the "Save Config" button for a new NAND
-re-open the new NAND with 360 Flash Tool
-Extract smc_config.bin while ticking "extract ibuild compatible files" under Options in 360 Flash Tool
-Inject smc_config.bin into my original NAND dump using: nandpro file.bin: -W16 smc_config.bin 3DF 1
-Flash my console with the file created in the above step via Flash 360

I think I just need to figure out the proper nandpro command for my Jasper 512MB NAND. I'll have to use W512 and 3Df 1 will be different as well...

Thx.

[l_oliveira]

Nope, that's not right, because the instructions I gave are for small block consoles.

If I had an large block console I could try something.

I believe that the smc_config file for a JASPER_BB console is 64KB, not 16KB....

Also, straight from nandpro help:

Code:

NandPro v2.0b by Tiros

Useage:

NandPro dev: -r# Filename (HexStartBlock HexBlockCount) ->Read
NandPro dev: -w# Filename (HexStartBlock HexBlockCount) ->Write
NandPro dev: -e# (HexStartBlock HexBlockCount)          ->Erase

dev: is hardware interface usb: or lpt:
dev: can also be a filename:, to be used as a 'Virtual Nand Device'
# is nand size (16, 64, 256, 512) in MegaBytes
(Optional) block ranges, defaults to entire device
-r# Reads saving file RAW (with ECC)
-R# Reads saving file without ECC
-w# Writes RAW (with ECC) file
+W# Write while ADDING ECC from file without ECC
+w# Write while FIXING ECC from RAW (with ECC) file

Meaning that it's +W, not -W for the command.  (But -W works and I don't know why lol)

[canderousa]

OKAY! I think I have a working image. I haven't flashed it yet, but I'm confident in it. I also avoided using nandpro.

With an idea from pkmz, I built a custom image (thanks for the tip man).

I basically took my modified smc_config.bin with all temps = 55C and built a "CUSTOM freeBOOT" using FreeBoot Toolbox Maker. I ticked "Jasper 512MB" and "Creating a custom freeBoot". When prompted with the freeBoot data folder, I copied my smc_config.bin to the "data" folder and continued the build.

The output image seems to check out nicely in 360 Flash Tool. I think this is a safe method of editing and injecting smc_config.bin.

[pkmz]

I don't use toolbox maker so not sure how it works. I used DOS and Fbbuild.

Yea, I used Flash 360 to edit my nand. I then saved. I reopened the nand I edit in Flash 360 dumped files and also set the option for "Freeboot" setup in options.

I then took the files needed to build the 12611 freeboot image and placed those in "mydata" folder.

built the new image and flashed through xellous.

Works like a charm. Also had all the fixes from Cory & Blackaddr for the PnC. Thanks guy you're the greatest.

[canderousa]

For anyone who cares, FreeBoot Toolbox Maker uses fbbuild command line to build the custom image for the user. It's essentailly the same thing. It just saves the user from entering command line....