Print

[krizalid]

Regarding...

QUOTE

* trinity CB_B patches updated to allow glitch image booting on official 14717 updated slims

Does this version of xeBuild make the image_00000000.ecc file to boot xell to obtain CPU key and fuses or do we have to wait for an update version of that tool?

[Swizzy]

QUOTE(krizalid @ Feb 22 2012, 07:00 AM)

Regarding...
Does this version of xeBuild make the image_00000000.ecc file to boot xell to obtain CPU key and fuses or do we have to wait for an update version of that tool?

That's for xeBuild only, which makes full nand images, it does NOT make ECC images so you'll have to wait for that...

[kopyone]

QUOTE

Updated fats will likely require new CPLD timing, if you wish to continue to glitch a fat for the time being it's advised to not apply any update ] 14699.

I have a fat jasper that is already glitched and on 14699.  Does this mean i should not install this xebuild with the new dash? Or is this just for the unglitched fat consoles that should not be updated before glitching?

Sorry, just a little confused.

[kero]

Got the warning when building:

'Could not find a non-zero CF LDV to use, setting it to 1 but that may be incorrect!"

Is there anywhere i can find out what exactly this error means?

[kero]

QUOTE(kero @ Feb 23 2012, 09:49 AM)

Got the warning when building:

'Could not find a non-zero CF LDV to use, setting it to 1 but that may be incorrect!"

Is there anywhere i can find out what exactly this error means?

Found the info: J-Tag images dont care what this value so i can ignore this warning

QUOTE

; byte 0x21f of decrypted CF (also is the count of 0xF in fuse rows 7 and
; if you provide a nanddump.bin with the correct ldv value, there is no reason to fill this in
; jtag images won't care what this value is set to, but glitch and retail images require this to match CPU fuses
; valid values are 1 - 32, leave blank to set to 0 for devkit images

[uN0pEn]

Thank you for your hard work Team xeBuild. I will give it a try!