Topic: FreeBOOT Toolbox 0.04 Maker v2.7.1a (Read 158 times)

Xbox-Scene · « **on:** June 27, 2011, 11:34:00 AM »

FreeBOOT Toolbox 0.04 Maker v2.7.1a
Posted by XanTium | June 27 13:34 EST | News Category: Xbox360

BestPig released a new version of freeBOOT ToolBox - a tool that allows to create and customize a freeBOOT image based on an original or XBR/freeBOOT dump:

Quote

A small update that will just add support for the 13146 kernel thanks to fbuild 0.31.

Official Site: http://www.bestpig.fr (the interface is also available in English)
Download: n/a (might be illegal under DMCA/EUCD)

clouduz · « **Reply #1 on:** June 27, 2011, 01:40:00 PM »

Good to see this is updated. It's the only one I always had success using. Thanks for the update notice (IMG:style_emoticons/default/smile.gif)

melkia · « **Reply #2 on:** June 27, 2011, 02:46:00 PM »

I have a 16mb jasper but this keeps failing in making a new fb.bin only when I select 256mb does it suceed

RRoD420 · « **Reply #3 on:** June 27, 2011, 02:53:00 PM »

don't choose auto-detect. and don't forget to manually insert smc if it's modified, this app doesn't use the smc.bin from the orig file!

Midnight Tboy · « **Reply #4 on:** June 27, 2011, 04:58:00 PM »

I have a jasper jtag which I bought pretagged (after my self-tagged xenon died for the last time).

Is there any way to know what version of SMC was used, other than taking the motherboard out and seeing where wires are?

melkia · « **Reply #5 on:** June 27, 2011, 05:08:00 PM »

holy shit I had no idea WOW I need to do that. Well I got the original smc from my original nand how do I combine this to get what the new freeboot image so that I can flash it. currently I am getting an E71 error so I have flashed it incorrectly

This post has been edited by melkia: Jun 28 2011, 12:25 AM

Twis7eD · « **Reply #6 on:** June 27, 2011, 05:09:00 PM »

QUOTE(Midnight Tboy @ Jun 27 2011, 05:58 PM)

I have a jasper jtag which I bought pretagged (after my self-tagged xenon died for the last time).

Is there any way to know what version of SMC was used, other than taking the motherboard out and seeing where wires are?

I don't believe so. Someone can correct me, though, if they think otherwise.

Also, nice job as always, Bestpig.

This post has been edited by Twis7eD: Jun 28 2011, 12:11 AM

turfster · « **Reply #7 on:** June 27, 2011, 05:11:00 PM »

QUOTE(Midnight Tboy @ Jun 27 2011, 06:58 PM)

I have a jasper jtag which I bought pretagged (after my self-tagged xenon died for the last time).

Is there any way to know what version of SMC was used, other than taking the motherboard out and seeing where wires are?

To get the smc.bin, take your updflash.bin or freeboot image that is on the jtag now, open it with 360_Flash_Tool_v0.97, enter your cpukey, click on extract, click on smc.bin and save to a folder.

Midnight Tboy · « **Reply #8 on:** June 27, 2011, 05:51:00 PM »

QUOTE(turfster @ Jun 28 2011, 12:11 AM)

To get the smc.bin, take your updflash.bin or freeboot image that is on the jtag now, open it with 360_Flash_Tool_v0.97, enter your cpukey, click on extract, click on smc.bin and save to a folder.

thanks - I was given the cd with the original nand, aswell as I believe the freeboot image on it. I'll take a look at it in the morning

Once I have that smc.bin file.....is it possible to look at it to see what method was used, standard/aud-clamp/whateverothersthereare? Just so if later down the line, I do use an all in one utility, which asks me to select which method, I'd know which to choose? As I've read where some have made their 360s nonbootable by selecting the wrong one (and I don't fancy having to go through process of relearning jtagging again (IMG:style_emoticons/default/smile.gif))

turfster · « **Reply #9 on:** June 27, 2011, 06:05:00 PM »

Not sure, I usually use best pigs toolbox maker(create custom image using my smc.bin from previous freeboot image)or manually create an image with fbbuild .31. So I would extract smc.bin, smc_config.bin and my kv.bin. Use that with fbbuild.

You can always open the 360 and see if he used transistors, most likely aud_clamp method.

This post has been edited by turfster: Jun 28 2011, 01:15 AM

tattoome25 · « **Reply #10 on:** June 27, 2011, 06:31:00 PM »

just taking a look, this version does away with the no dvd drive option as i have taken mine out and replaced with 1tb hdd?

tattoome25 · « **Reply #11 on:** June 27, 2011, 08:13:00 PM »

so i updated all went fine but my second profile on hdd shown as being corrupted,flash back to 12611 and both profiles showed up fine and usable, any clues to why it did that?

Obveron · « **Reply #12 on:** June 28, 2011, 08:18:00 AM »

modded profiles are corrupted with 13146. best create a new offline profile from scratch. you can re-sign saved games with Modio.

uk_dan2k · « **Reply #13 on:** June 28, 2011, 10:00:00 AM »

hi all,

anyone know if this supports mismatched keyvaults (to get rid of xmas lights) like older versions have for 12611.

thanks for any help

pudink · « **Reply #14 on:** June 28, 2011, 10:27:00 AM »

QUOTE(tattoome25 @ Jun 28 2011, 03:13 AM)

so i updated all went fine but my second profile on hdd shown as being corrupted,flash back to 12611 and both profiles showed up fine and usable, any clues to why it did that?

AFTER UPDATING TO 13146
when we create a new profile and sign the saves with modio,can we just re-sign the avatar dlc that we have downloaded from the internet?Or does it detect the avatar dlc and corrupts the profile immediately?...

if it still corrupts the profile and we cant sign new avatar dlc on 13146 then all the stuff on the internet is useless now.What a shame (IMG:style_emoticons/default/blink.gif)

This post has been edited by pudink: Jun 28 2011, 05:27 PM

Author Topic: FreeBOOT Toolbox 0.04 Maker v2.7.1a (Read 158 times)