360 Multi Builder *support* Options

[ThE MaSTeR 3]

what is a cb? I have 2 jasper that I plan on glitching that I've recently updated to the latest dash. Is the CB something that you have no control over which you get or does it change when up update or something?

[Rogero]

Sorry, what is this about some CBs being not glitchable? I thought the glitch hack would work for ANY 360 except Xenons... Did I miss some news?

Jasper cb_6752 / Falcon cb_5772 & any FAT that has a 2-part CB (CB_A and CB_B) are not glitchable at all because they are not compatible with the Glitch Hack at the moment.

You can Open your nand dump with 360FlashToolv0.97 and you can see your 2BL / [CB] version.

I had reports about latest Slim board revision released (Corona) which had the Hana chip removed that makes it not compatible at all with the Glitch Hack too.

[blastagator]

what is a cb? I have 2 jasper that I plan on glitching that I've recently updated to the latest dash. Is the CB something that you have no control over which you get or does it change when up update or something?

You can't downgrade the CB because whenever it is upgraded efuse blows preventing older ones from loading. CB can be upgraded with dashboard update (that's how they fixed the original jtag glitch)

[Chan163]

So the big talk of ALL the consoles to date being glitchable when the glitch came out and not being fixable by M$ is a big pile of BS?

Under which circumstances would a console have a 6752, a 5772 or a 2-part CB? This depending on what?

This post has been edited by Chan163: Nov 4 2011, 02:23 AM

[blastagator]

So the big talk of ALL the consoles to date being glitchable when the glitch came out and not being fixable by M$ is a big pile of BS?

Under which circumstances would a console have a 6752, a 5772 or a 2-part CB? This depending on what?

Shortly after release they said phats could be patched, slim can't be. Slim glitches CB_A, and quote from the release of the hack:

"Now, maybe you haven't realised yet, but CB_A contains no checks on revocation fuses, so it's an unpatchable hack !"

AKA the fat they could patch CB_B and blow a fuse and you're F***ed. Slim they can't do that

This post has been edited by blastagator: Nov 4 2011, 04:53 AM

[ThE MaSTeR 3]

So if you are on the latest dash with a jasper you have the 6752 CB?

[Mthodmn101]

So if you are on the latest dash with a jasper you have the 6752 CB?

no.... when u dump ur nand, ull find out ur CB

[djexentrix]

Hmm I wonder what specific update patches the CB as it would be nice to know what to look for without having to dump the nand.

[ThE MaSTeR 3]

Hmm I wonder what specific update patches the CB as it would be nice to know what to look for without having to dump the nand.

exactly. is it just random with any dash update? If I cant glitch one of my jaspers because I recently updated Im going to be pissed. I was remembering the "every 360 is glitchable no matter the dash or model!!" when I updated them.

nov 2008 (one of first jasper batches) and august 2009.

This post has been edited by ThE MaSTeR 3: Nov 4 2011, 05:09 AM

[Mthodmn101]

exactly. is it just random with any dash update? If I cant glitch one of my jaspers because I recently updated Im going to be pissed. I was remembering the "every 360 is glitchable no matter the dash or model!!" when I updated them.

nov 2008 (one of first jasper batches) and august 2009.

CB has nothing to do with dash updates... u can only find out by dumping the nand

[geekay]

Was glad to see support for cb6751 on bb 512 nands since I just happened to have one that I started working on but it doesn't seem to boot. Flashing back to stock works fine so although 6751 should work it doesn't seem to always work.

[ThE MaSTeR 3]

CB has nothing to do with dash updates... u can only find out by dumping the nand

ok I'lll stop worrying about it and find out when I dump my nand(s)

[wlintek]

did a slim using 360 Mult Builder v0.2, xell image worked ok, but after flashing the hacked 13604 image and booted the fan run a lot faster. i then used v0.1 to build a second image and flashed again, this fixed fan issue. does any one have the same issue with v0.2?

[scoltar]

This talk of some jasper models not being compatible with the glitch hack has really brought out the pessimist in me. I have one brand new one from 2010 I was planning to do when I could get my hands on a coolrunner and nand-x. Anyone have any idea of how common these unglitchable jaspers are? I'm honestly a noob on this stuff, but I thought I would try it out for myself this time around. That being said, can anyone recommend a good tutorial on using a nand-x to dump the nand?

[Rogero]

did a slim using 360 Mult Builder v0.2, xell image worked ok, but after flashing the hacked 13604 image and booted the fan run a lot faster. i then used v0.1 to build a second image and flashed again, this fixed fan issue. does any one have the same issue with v0.2?

in version 0.2 i forgot the Fan Speed parameters in file "Data\my360\options.ini" set both to "cpufan=70, gpufan=70" if anyone wants them back to default you can just edit the "options.ini" file and set them back to:
cpufan=
gpufan=
(just delete the value 70 from both lines) and the Fan speed will be set to default again.

in version 0.1 it is already set to default, and for slim machines both versions 0.1 / 0.2 generates the same Slim images nothing changed.

This talk of some jasper models not being compatible with the glitch hack has really brought out the pessimist in me. I have one brand new one from 2010 I was planning to do when I could get my hands on a coolrunner and nand-x. Anyone have any idea of how common these unglitchable jaspers are? I'm honestly a noob on this stuff, but I thought I would try it out for myself this time around. That being said, can anyone recommend a good tutorial on using a nand-x to dump the nand?

Jaspers with cb_6752 (un-glitchable) are usually rare, only few un-lucky persons have them.

This post has been edited by Rogero: Nov 4 2011, 05:45 PM