RGH Jasper BB 256 w/ dvd drive issue...

[grpracing]

Ok, ive pulle the jasper out of the closet and desided to install the coolrunner ver b in it. Nand is run thru multibuilder and everything works fine.

The reason the jasper was tossed aside was the lite-on drive went thru meltdown and dvd key was un retrievable till now. I don't have a lite- on drive atm but have a pile of good sammy m28 drives and plan to leave the coolrunner in the system. I really would like this thing to read games to make it easier to baack them up onto my harddrive.

I have a ck3 lite and the recommended via 6421 board with working knowledge of flashing the drives. I have been reading post after post about this and need it cleared up.... Can i get the sammy drive to work in the jasper and if so can someone help me out with the proper way to flash it. I have attempted to spoof one in as a lite-on but it still gives that wonderful message. My log from multibuilder showed now errors with the frct.bin file . i just want to finish this thing and move on to my next one when the demon coems out!! I have a few xenon systems to get going again. lol.

Come on guys please help cause other than this the coolrunner is the greatest addition to an xbox I have ever used.

 

[gerardo15]

Once you have rgh you dont have to spoof anything. Just put the key in the sammy. And it will work.

 

[grpracing]

that's the problem. ive tried it both ways and still no go.

 

[ball00]

You can try to rebuild your nandflash image with xebuild and disable the FCRT.bin check If you haven't already

 

[grpracing]

ok, now is this a typical or non typical problem with the jaspers? Ive been reading allot and the bin file seems to be the problem in most cases but i don't see allot of this problem coming up.

just want to know for the future. I am having a ball with the nand flashing and sounds like thanx to tx this will just be the beginning. lol

 

[ball00]

Not really up on jaspers atm so I don't know. Did that work though?

 

[grpracing]

I will let you know shortly. Im downloading xebuild right now. Is it worth adding the 14699 dash while im at it?

 

[ball00]

I'd be tempted to try and get the drive working first off then update. You don't want any more issues in the mix yet.

 

[grpracing]

good point. I found this in the read me.txt and figured i would post it for others like me with this problem.

Notes about FCRT patches
======================================================================

This patch removes the need for FCRT.bin in nand, however, it will
NOT work for everyone, it's been enabled in the default configuration,
but should be disabled if you are using a machine with a Liteon DG16-D5S
FW: 1175, it's been confirmed by me that it doesn't work on these drives
all others i've tested has worked just fine, however it can still be a
problem for you to have this activated, disable it if games don't work
from discs (if you use this feature!)

 

[grpracing]

this is going to take a bit cause ive never used xebuilder .

 

[grpracing]

ok does this log look right?

==================================
 Swizzy's xeBuild GUI version 1.0
Log Started: Sunday 2/5/2012 12:03:48 AM
==================================
Using custom Xell
ERROR: Cannot create a Glitch image without xell! defaulting to xell-reloaded!
Including dashlaunch... Done!
Including custom dashlaunch settings (launch.ini)... Done!
Copying nand to data dir, this may take a while... Done!
Checking if SMC is Glitch or Retail...
Dumping current SMC... Done!
Checking SMC...
SMC is Retail!
checking if you selected patchsmc or not...

Parameters sent to xeBuild:

-noenter -t glitch -c jasper256 -d data -f 13604 -b DD88AD0C9ED669E7B56794FB68563EFA -p 2301C1CBA4C7294F4B9F64FDD3D49111 -o xellbutton=eject -o nosecurity -o cpufan=0 -o gpufan=0 -o cputemp=0 -o patchsmc -o nandmu output.bin

Building nand using xeBuild (this may take a while):

---------------------------------------------------------------
     xeBuild v1.00.356
---------------------------------------------------------------
building glitch image
***** WARNING: fcrt.bin not found, skipping *****
---------------------------------------------------------------
output.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB (system only)
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  : 2301C1CBA4C7294F4B9F64FDD3D49111
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
CF LDV   : 3
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Removing previously built image... Done!
Moving output file to output location, this may take a few minutes... Done!
Cleaning data and temporary directories...Done!


****** The app has now finished! ******

 

[grpracing]

ok, ive also been informed that since this jasper has dash 13604 running on it instead of 13599 there may be a problem with that as well. Ive tried changing the osig in the nand to the sammy drive using 360 nand flasher but still getting the "use an xbox to read this disk" friggin message. Anyone have any ideas?

 

[x360ccm]

how are you puttin the key onto the drive.

 

[Martin C]

Jeez! I hate finding threads like this that go off in the wrong direction!

fcrt.bin - 100% irrelevent. Only slim consoles have this file, so ignore any errors.

Just flash your Samsung MS28 with LT2.01 (no need to spoof the OSIG) with your DVD key. I would install dashlaunch 2.27 too. All should be fine.

 

[grpracing]

thanks for the suggestion martin but if it was that easy it would have been done already.
this is the nand.bin.log maybe i am overlooking something in here.

---------- Post added at 11:12 ---------- Previous post was at 11:08 ----------

the nand.bin.log

  ---------------------------------------------------------------
     ggBuild v0.33.273
---------------------------------------------------------------
data directory overridden from command line to '13604'
per build directory overridden from command line to 'my360'
file name overridden from command line to 'nandflash.bin'

------ parsing user ini at '.\my360\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0xe6 bytes in memory
loading cpukey.txt from .\my360\cpukey.txt
CPU Key set to: 0x2301C1CBA4C7294F4B9F64FDD3D49111
setting 1blkey from ini: 0x................................
1BL Key set to: 0x................................ sum: 0x983 (expects: 0x983)
Using nonandmu option (ini file)
Using patchsmc option (ini file)

------ Checking .\my360\nanddump.bin ------
Loading NAND dump...done!
NAND dump is from a big block machine
NAND dump uses big block controller
parsing dump into user and spare...
done!
decrypting KeyVault at address 0x4000 of size 0x4000
keyvault decrypted OK, will use if no kv.bin is provided
decrypting SMC at address 0x1000 of size 0x3000
SMC decrypted OK, will use if no external smc.bin is provided
seeking smc config in dump...found at offset 0x3be0000! Using if no smc config is provided.
CF slot 0 decrypted ok LDV 0x03 Pairing: 0xa31c9f
CF slot 1 decrypted ok LDV 0x02 Pairing: 0xa31c9f
setting LDV from image to 3
setting pairing data from image to 0xa31c9f
MobileB.dat found at page 0x1c1b0, size 2048 (0x800) bytes
MobileC.dat found at page 0x1c100, size 512 (0x200) bytes
MobileD.dat found at page 0x1c104, size 2048 (0x800) bytes
MobileE.dat found at page 0x1c1bc, size 1536 (0x600) bytes

------ parsing ini at '.\13604\filelist.ini' ------
ini version 13604

ini: label [jasperbl] found
found (1) 'cb_6750.bin' crc: 0xf7afa8cc
found (2) 'cb_bnone.bin' crc: 0x00000000
found (3) 'cd_8453.bin' crc: 0x25e0acd0
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_13604.bin' crc: 0x639a4cd7
found (6) 'cg_13604.bin' crc: 0x7e9f5364

ini: label [flashfs] found
found (1) 'aac.xexp' crc: 0xdaed8bc7
found (2) 'bootanim.xex' crc: 0x8a7ab1b4
found (3) 'createprofile.xex' crc: 0xe19ca8c4
found (4) 'dash.xex' crc: 0xecdaf6c0
found (5) 'deviceselector.xex' crc: 0xaa4579d1
found (6) 'gamerprofile.xex' crc: 0xebc5fec3
found (7) 'hud.xex' crc: 0xe2410ee1
found (8) 'huduiskin.xex' crc: 0x390eac39
found (9) 'mfgbootlauncher.xex' crc: 0xf3637ed9
found (10) 'minimediaplayer.xex' crc: 0x23d28bb8
found (11) 'nomni.xexp' crc: 0xed7cd3f5
found (12) 'nomnifwk.xexp' crc: 0x2c6fd7e8
found (13) 'nomnifwm.xexp' crc: 0xaa978831
found (14) 'signin.xex' crc: 0xf7436a62
found (15) 'updater.xex' crc: 0xd0cd6753
found (16) 'vk.xex' crc: 0x65f4eec0
found (17) 'xam.xex' crc: 0x2a74ee0f
found (18) 'xenonclatin.xtt' crc: 0xd5d17ff5
found (19) 'xenonclatin.xttp' crc: 0x7a507ad1
found (20) 'xenonjklatin.xtt' crc: 0xdde4a14c
found (21) 'xenonjklatin.xttp' crc: 0x945b7092
found (22) 'ximecore.xex' crc: 0xccb87938
found (23) 'ximedic.xex' crc: 0x1d992bfb
found (24) 'ximedic.xexp' crc: 0x47a55af9
found (25) 'launch.xex' crc: 0x00000000
found (26) 'lhelper.xex' crc: 0x00000000

ini: label [security] found
found (1) 'crl.bin' crc: 0x00000000
found (2) 'dae.bin' crc: 0x00000000
found (3) 'extended.bin' crc: 0x00000000
found (4) 'fcrt.bin' crc: 0x00000000
found (5) 'secdata.bin' crc: 0x00000000
------ ini parsing completed ------

output name overridden to: nandflash.bin

Writing initial header to flash image

------ Loading bootloaders and required security files ------
reading .\my360\smc.bin failed, using smc.bin from nand dump
reading .\my360\kv.bin failed, using kv.bin from nand dump
reading .\13604\cb_6750.bin (0x9a40 bytes) (crc32: 0xf7afa8cc ini: 0xf7afa8cc)
reading .\13604\cd_8453.bin (0x5780 bytes) (crc32: 0x25e0acd0 ini: 0x25e0acd0)
reading .\13604\ce_1888.bin (0x5606a b pad 0x56070 b) (crc32: 0xff9b60df ini: 0xff9b60df)
reading .\my360\xell-gggggg.bin (0x40000 bytes)
reading .\13604\cf_13604.bin (0x4450 bytes) (crc32: 0x639a4cd7 ini: 0x639a4cd7)
reading .\13604\cg_13604.bin (0x659e0 bytes) (crc32: 0x7e9f5364 ini: 0x7e9f5364)
reading .\13604\bin\patches_fat.bin (0x6dc bytes)
reading .\my360\smc_config.bin failed, using smc_config.bin from nand dump
-------------------
checking smc_config
-------------------
extracting config
------------------
SMC config info:
------------------
Target temps: Cpu:  80øC Gpu:  71øC Edram:  73øC
Max temps   : Cpu:  95øC Gpu:  90øC Edram:  92øC
Cpu Fan     : (auto)
Gpu Fan     : (auto)
MAC Address : 00:22:48:2e:97:1d
AVRegion    : 0x00000100 (NTSC-M)
GameRegion  : 0x00ff (NTSC/US)
DVDRegion   : 1
resetKey    : XXUD
---------------------
Checking ini for smc config data patches
smc was not patched
---------------------
done!

------ Encrypting and finalizing bootloaders ------
SMC checksum: 5b3aed00
clean SMC found, type: Jasper 2.3
patching clean smc, type: Jasper 2.3 offset: 0x12ba
clean SMC hacked successfully
done!

------ Adding bootloaders to flash image ------
adding smc.bin to 0x00001000 len 0x3000
adding kv.bin to 0x00004000 len 0x4000
adding cb_6750.bin to 0x00008000 len 0x9a40
adding cb_bnone.bin to 0x00011a40 len 0x0
adding cd_8453.bin to 0x00011a40 len 0x5a40
adding ce_1888.bin to 0x00017480 len 0x56070
adding xell-gggggg.bin to 0x00070000 len 0x40000
adding cf_13604.bin to 0x000b0000 len 0x4450
adding cg_13604.bin to 0x000b4450 len 0x659e0
adding patches_fat.bin to 0x000c0010 len 0x3e8
Writing CG patch slot overflow data to sysupdate.xexp1...done!

------ adding 26 firmware files ------
reading .\13604\aac.xexp (0x4800 bytes) (crc32: 0xdaed8bc7 ini: 0xdaed8bc7)
reading .\13604\bootanim.xex (0x55000 bytes) (crc32: 0x8a7ab1b4 ini: 0x8a7ab1b4)
reading .\13604\createprofile.xex (0xc000 bytes) (crc32: 0xe19ca8c4 ini: 0xe19ca8c4)
reading .\13604\dash.xex (0x5e7000 bytes) (crc32: 0xecdaf6c0 ini: 0xecdaf6c0)
reading .\13604\deviceselector.xex (0x9000 bytes) (crc32: 0xaa4579d1 ini: 0xaa4579d1)
reading .\13604\gamerprofile.xex (0x1a000 bytes) (crc32: 0xebc5fec3 ini: 0xebc5fec3)
reading .\13604\hud.xex (0x1f000 bytes) (crc32: 0xe2410ee1 ini: 0xe2410ee1)
reading .\13604\huduiskin.xex (0x11000 bytes) (crc32: 0x390eac39 ini: 0x390eac39)
reading .\13604\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0xf3637ed9 ini: 0xf3637ed9)
reading .\13604\minimediaplayer.xex (0xc000 bytes) (crc32: 0x23d28bb8 ini: 0x23d28bb8)
reading .\13604\nomni.xexp (0xd000 bytes) (crc32: 0xed7cd3f5 ini: 0xed7cd3f5)
reading .\13604\nomnifwk.xexp (0x2000 bytes) (crc32: 0x2c6fd7e8 ini: 0x2c6fd7e8)
reading .\13604\nomnifwm.xexp (0x5000 bytes) (crc32: 0xaa978831 ini: 0xaa978831)
reading .\13604\signin.xex (0x12000 bytes) (crc32: 0xf7436a62 ini: 0xf7436a62)
reading .\13604\updater.xex (0x8000 bytes) (crc32: 0xd0cd6753 ini: 0xd0cd6753)
reading .\13604\vk.xex (0x9000 bytes) (crc32: 0x65f4eec0 ini: 0x65f4eec0)
reading .\13604\xam.xex (0x218000 bytes) (crc32: 0x2a74ee0f ini: 0x2a74ee0f)
reading .\13604\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
reading .\13604\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
reading .\13604\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
reading .\13604\xenonjklatin.xttp (0x7000 bytes) (crc32: 0x945b7092 ini: 0x945b7092)
reading .\13604\ximecore.xex (0x15000 bytes) (crc32: 0xccb87938 ini: 0xccb87938)
reading .\13604\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
reading .\13604\ximedic.xexp (0x2800 bytes) (crc32: 0x47a55af9 ini: 0x47a55af9)
reading .\13604\launch.xex (0x9000 bytes)
reading .\13604\lhelper.xex (0x6000 bytes)

------ adding 5 security files ------
reading .\my360\crl.bin (0x9e0 bytes)
writing as crl.bin to flash
reading .\my360\dae.bin (0xad30 bytes)
writing as dae.bin to flash
reading .\my360\extended.bin (0x4000 bytes)
writing as extended.bin to flash
***** could not read fcrt.bin, skipping *****
reading .\my360\secdata.bin (0x400 bytes)
writing as secdata.bin to flash

------ checking for Mobile*.dat ------
MobileB.dat was found in dump, 0x800 bytes, adding type 0x31
MobileC.dat was found in dump, 0x200 bytes, adding type 0x32
MobileD.dat was found in dump, 0x800 bytes, adding type 0x33
MobileE.dat was found in dump, 0x600 bytes, adding type 0x34

------ adding smc_config.bin ------

------ finalizing image ------
Fixing up empty FS block entries...done!
Writing FS table to image...done!
fixing up big block LBA numbers in spare...done!
calculating ECD bytes and assembling raw image...done!
writing file 'nandflash.bin' to disk...done!
nandflash.bin written OK

---------------------------------------------------------------
nandflash.bin glitch image built, info:
---------------------------------------------------------------
console  : jasper (big block)
NAND size: 64MiB (system only)
CPU Key  : 2301c1cba4c7294f4b9f64fdd3d49111
1BL Key  : ................................
CF LDV   : 3
---------------------------------------------------------------
    ggBuild Finished. Have a nice day.
---------------------------------------------------------------

 

[ball00]

Sorry wrong direction was my fault. I had this problem with a slim didn't realise it was only slims. Learnt from that. OP's already tried flashing and inserting dvd key.

 

[rdubbs007]

Removed the 1BL key from post, probably shouldnt have that in there

 

[superspeed]

Removed the 1BL key from post, probably shouldnt have that in there

Should probably edit out the CPU key as well. :tongue:

---------- Post added at 11:25 ---------- Previous post was at 11:24 ----------

Also the 1BL is still in post #11

 

[Martin C]

Post your JF log please.

 

[RavenPhoenix]

Jeez! I hate finding threads like this that go off in the wrong direction!

fcrt.bin - 100% irrelevent. Only slim consoles have this file, so ignore any errors.

Just flash your Samsung MS28 with LT2.01 (no need to spoof the OSIG) with your DVD key. I would install dashlaunch 2.27 too. All should be fine.

Thank you Martin for making that statement.

I was helping grpracing through PM's and I already tried explaining that to him but I guess he just may of needed further clarification.

Anyhow, from what I have been told so far I think he is having problems with getting the Sammy drive that he's got working as a spoofed drive in his console which had a LiteOn as an original.

If it is a RGH then any drive in the console should work but if you are still getting the Play DVD issue then have you confirmed your DVD Key is correct? Are you using back ups or originals to test?