Unsolved XeBuild error trying to update to newest dashboard

PureTryHardd

Enthusiast
Messages
100
Reaction score
10
Using xell-reloaded for Glitch hack
Including dashlaunch... Done!
Including custom dashlaunch settings (launch.ini)... Done!
Copying nand to data directory, this may take a while... Done!
Checking if SMC is Glitch or Retail...
Dumping current SMC... Done!
Checking SMC...
SMC is Glitch patched! it will be used the way it is...
Disabling FCRT.bin check...
Parameters sent to xeBuild:
-noenter -t glitch -c trinity -d data -f 17544 -b DD88AD0C9ED669E7B56794FB68563EFA -p 5757B1C4AD4F7AB99A248047B4B28187 -a nofcrt output.bin
Building nand using xeBuild (this may take a while):
---------------------------------------------------------------
xeBuild v1.19.808
---------------------------------------------------------------
base path changed to C:\Users\timot\Desktop\xeBuild_GUI_2.098 (17544)\files
---- { Image Build Mode } ----
building glitch image
done! fsroot found ok!

***** ERROR: fcrt.bin not found, keyvault has this file flagged as required but it's being skipped *****
note - on hacked images a nofcrt patch WILL NOT allow the drive to function
but should allow the machine to boot normally
---------------------------------------------------------------
output.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17544.0
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 033806122343
ConsoleId : 446901893992
MoboSerial: 7910239201672235
Mfg Date : 06/06/2012
CPU Key : 5757B1C4AD4F7AB99A248047B4B28187
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : CB0BDE3325BE524D36E300219C37D29C
CF LDV : 5
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Moving output to your destination directory... Done!
Cleaning data and temporary directories... Done!





Please help!
 

Connor

Hi :3
Retired
Messages
2,144
Reaction score
1,293
Using xell-reloaded for Glitch hack
Including dashlaunch... Done!
Including custom dashlaunch settings (launch.ini)... Done!
Copying nand to data directory, this may take a while... Done!
Checking if SMC is Glitch or Retail...
Dumping current SMC... Done!
Checking SMC...
SMC is Glitch patched! it will be used the way it is...
Disabling FCRT.bin check...
Parameters sent to xeBuild:
-noenter -t glitch -c trinity -d data -f 17544 -b DD88AD0C9ED669E7B56794FB68563EFA -p 5757B1C4AD4F7AB99A248047B4B28187 -a nofcrt output.bin
Building nand using xeBuild (this may take a while):
---------------------------------------------------------------
xeBuild v1.19.808
---------------------------------------------------------------
base path changed to C:\Users\timot\Desktop\xeBuild_GUI_2.098 (17544)\files
---- { Image Build Mode } ----
building glitch image
done! fsroot found ok!

***** ERROR: fcrt.bin not found, keyvault has this file flagged as required but it's being skipped *****
note - on hacked images a nofcrt patch WILL NOT allow the drive to function
but should allow the machine to boot normally
---------------------------------------------------------------
output.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17544.0
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 033806122343
ConsoleId : 446901893992
MoboSerial: 7910239201672235
Mfg Date : 06/06/2012
CPU Key : 5757B1C4AD4F7AB99A248047B4B28187
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : CB0BDE3325BE524D36E300219C37D29C
CF LDV : 5
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Moving output to your destination directory... Done!
Cleaning data and temporary directories... Done!





Please help!
I see you have a trinity.

On Slim systems this check needs to be disabled before creating the new nand file.

Simply check the box "Disable FCRT.bin check" and build the nand again, should work normally!

For more clarification watch this video and skip to around 7:45 for an explanation/exactly what you need to do.

 

NighttimeHawk

Matrix Trident, Icedcube XenochipGC, Slim XDK
Messages
322
Reaction score
45
I see you have a trinity.

On Slim systems this check needs to be disabled before creating the new nand file.

Simply check the box "Disable FCRT.bin check" and build the nand again, should work normally!

For more clarification watch this video and skip to around 7:45 for an explanation/exactly what you need to do.

His log says “Disabling FCRT.bin check...” in the middle of it though
 

Connor

Hi :3
Retired
Messages
2,144
Reaction score
1,293
His log says “Disabling FCRT.bin check...” in the middle of it though
You're right, overlooked the whole damn thing I guess!

P PureTryHardd I've reread this error you're getting. This pops up when you're trying to manually flash a KV to the NAND and as such, causes extra steps to be taken. Before trouble shooting further, are you wanting to attempt this? I'd have to ask why as most stealth servers nowadays do all the KV managing, in other words, flashing the KV is an obsolete solution.
 

PureTryHardd

Enthusiast
Messages
100
Reaction score
10
You're right, overlooked the whole damn thing I guess!

P PureTryHardd I've reread this error you're getting. This pops up when you're trying to manually flash a KV to the NAND and as such, causes extra steps to be taken. Before trouble shooting further, are you wanting to attempt this? I'd have to ask why as most stealth servers nowadays do all the KV managing, in other words, flashing the KV is an obsolete solution.
I was updating kernel not flashing kv, although I used to change kvs like that in the past. Disc drive is not reading discs now. Is it even possible to fix? BTW I got that error when I checked the box "FCRT.bin check" I tried both ways and still got same error...
 
I see you have a trinity.

On Slim systems this check needs to be disabled before creating the new nand file.

Simply check the box "Disable FCRT.bin check" and build the nand again, should work normally!

For more clarification watch this video and skip to around 7:45 for an explanation/exactly what you need to do.

I Got the error when I checked the box too :/
 
Everything works just fine, but I think this might be the reason my disc drive is not reading games anymore...
 
Top Bottom