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

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
ok, using jungleflasher 1.91b, I have spoofed original fw, used donated firmware and manually spoofed the dvd key in, I test every time to make sure the drive has correct fw and dvd key. Ive tried jf's stock firmware ect. I am using a ck lite and a via 6421 board with no problems except i cant get this jasper to take a bite.

As i said in original post i have done the home work and followed everything i could find to correct this problem, still no avail. here is the jf logs from a few minutes ago...
Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JungleFlasher 0.1.91 Beta (300)

Session Started Tue Feb 07 20:26:31 2012



This is a 32 bit process running on a 32 bit CPU 

portio32.sys Driver Installed 

portio32.sys Driver Started, thanks Schtrom ! 

Found 4 I/O Ports.

Found 3 Com Ports.

Found 4 windows drives A: C: D: E:

Found 2 CD/DVD drives D: E:





Sending Sammy_Un_Lock to Drive on port 0xEE00

Stage 1, Complete!

Stage 2, Complete!

Stage 3, Complete!

Done!

Sending Vendor Intro

Requesting Device ID

Manufacturer ID: 0xBF

Device ID: 0xB6

Flash Name:  SST(SST39SF020)

Flash Size:  262144 bytes

Sending Vendor Intro to port 0xEE00



Parallel flash found with Status 0x70



Sending Device ID request to port 0xEE00

Manufacturer ID: 0xBF

Device ID: 0xB6

Flash Name:  SST(SST39SF020)

Flash Size:  262144 bytes

Loading firmware file C:\Users\Administrator\Desktop\Everything to Flash\JungleFlasher (LT+ 3.0)\Firmware\Stock Firmware\Samsung\Samsung_Post_13141\Sam_CFWtest.bin

MD5 hash:  5bdeb835a6fcc76b78bd799702fa2459

Inquiry string found

Identify string found

Drive key @ 0x4140 0907DEB9CD91C734E1E79F9E1F8B278E

Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]

Spoofed As:    [PLDS    DG-16D2S        0251]

Firmware is:  Stock                           

Loading firmware file C:\Users\Administrator\My Documents\SAM-OFW.bin

MD5 hash:  345a635e4d051ed0b6da7aad7ba917f5

Inquiry string found

Identify string found

Drive key @ 0x4212 52D69A5C9EEFA94B2D11EB80A2D67A6C

Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]

Firmware is:  Stock                           

Loading firmware file C:\Users\Administrator\Desktop\Everything to Flash\JungleFlasher (LT+ 3.0)\Firmware\4.bin

MD5 hash:  49ba387e97664fbea2a716c70a6a15b2

Inquiry string found

Identify string found

Drive key @ 0x406E 0907DEB9CD91C734E1E79F9E1F8B278E

Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]

Firmware is:  LT v2.01                        

Spoofing Target

DVD Key copied to target

ID strings already match





Getting Status from port 0xEE00

Parallel flash found with Status 0x70

Writing target buffer to flash



Sending Chip Erase request to port 0xEE00

Erasing:............

Writing Bank 0: ................

Writing Bank 1: ....y............

Writing Bank 2: ................

Writing Bank 3: ................



Flash Verification Test !

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: .........x.......

Write verified OK !



Sending Vendor Outro to port 0xEE00
and after the flash ...this is the test..
Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JungleFlasher 0.1.91 Beta (300)

Session Started Tue Feb 07 20:33:11 2012



This is a 32 bit process running on a 32 bit CPU 

portio32.sys Driver Installed 

portio32.sys Driver Started, thanks Schtrom ! 

Found 4 I/O Ports.

Drive type Un-determined

Found 3 Com Ports.

Found 4 windows drives A: C: D: E:

Found 2 CD/DVD drives D: E:





Key found in KeyDB at record (4 - Samsung_Post_13141)

Key is: 0907DEB9CD91C734E1E79F9E1F8B278E

Key has been tested and verified, thanks C4eva ! 

Drive is Samsung..


---------- Post added at 20:50 ---------- Previous post was at 20:43 ----------

also as a side note cause im surprised this hasnt been asked but i have already checked the pots on the laser to make sure it was in range. reads dvds great without a problem.
 

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
another note... I have just finished trying a third sammy drive and still no go. they check fine but the jasper doesnt like them. I still have a feeling that the problem is in a setting on the nand but I cannot seem to find it. Anyone have any other ideas???
 

RavenPhoenix

Senior Member
Mar 25, 2011
135
0
Sydney OZ
www.consoleme.webs.com
another note... I have just finished trying a third sammy drive and still no go. they check fine but the jasper doesnt like them. I still have a feeling that the problem is in a setting on the nand but I cannot seem to find it. Anyone have any other ideas???
Hey mate, just wanted to confirm that this BB Jasper has in fact been RGH'ed right? Also, are the disk that you tried originals or backups? I'm trying to throw a few ideas around to see if we could come up with something to help sort your issue out cause this one seems to be weird one.
 
  • Like
Reactions: grpracing

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
Thanks raven... Yeah its a 256 bb jasper. The disks are original not copies. Its runner the coolrunner board and works great other than i still cannot get it to accept a new dvd drive.
 

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
3 drives have been checked as of 1 hr ago so i doubt a drive fault here.
 

RavenPhoenix

Senior Member
Mar 25, 2011
135
0
Sydney OZ
www.consoleme.webs.com
3 drives have been checked as of 1 hr ago so i doubt a drive fault here.
Yep, defo can't be a drive fault if you have tried three and if all three drives were pulled from known working consoles.

Did you get any bad blocks when you dumped your nand? If you are unsure then can I get you to redump your nand with the nand-x and let me know if you have any at all please.
 
  • Like
Reactions: grpracing

cj_goalie31

VIP Member
Jan 7, 2012
275
33
Canada
All i can say is good luck because im by no means an expert and i will have to leave this one to the people that know what they are talking about
 

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
no bad blocks, raven. The nand went smooth and clean. I just dont understand it. I have the logs from the nand flash posted in here too. this jasper has never seen a rrod just had the drive go bad. trusted another guy to check it out and plugged the drive in upside down and smoked the drive. Ive been draggin it around for 3 years playing demos on it once in a while till the coolrunner. now im almost there if i could just get the drive to read games would be perfect and i could go back to working on the 3 xenon systems preparing for the demon to come out.
 

RavenPhoenix

Senior Member
Mar 25, 2011
135
0
Sydney OZ
www.consoleme.webs.com
oK, In that case can you try the following for me please:

Build a 14699 hacked image with XeBuild or Multi-builder depending on what your preference is. Please use your original unhacked nand image to build the image then once completed, write the image to the nand with raw flash via Xell.

Meanwhile, I will try and replicate this issue tonight cause I have a RGH Jasper here with a LiteOn orig drive and I also have the Sammy MS28 drive. I'll see if I could somehow get the console into the same situation as your in and that way I can troubleshoot this issue for you a little easier.
 
  • Like
Reactions: grpracing

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
OK, Sounds good. I will have to get on this tomorrow cause i have to get up early but I will give it a shot.
 

x360ccm

BANNED
Jan 18, 2011
3,616
0
south coast UK
i was sent 2 nands here pics.and i built a image using multibuild for him just got to wait and see if it works.

and here is the log

---------------------------------------------------------------
xeBuild v1.00.356
---------------------------------------------------------------
building glitch image
per build directory overridden from command line to 'my360'
data directory overridden from command line to '14699'
Using PATCHSMC option
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, 0x14b bytes in memory
loading cpukey.txt from .\my360\cpukey.txt
CPU Key set to: 0x23===========111
setting 1blkey from ini: 0x
1BL Key set to: 0x sum: 0x983 (expects: 0x983)
xex Key set to: 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)
------ parsing ini at '.\14699\_glitch.ini' ------
ini version 14699
ini: label [jasperbl] found
found (1) 'cb_6750.bin' crc: 0xf7afa8cc
found (2) 'none' crc: 0x00000000
found (3) 'cd_8453.bin' crc: 0x25e0acd0
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_14699.bin' crc: 0x6fb4d90e
found (6) 'cg_14699.bin' crc: 0xbccc9fe1
ini: label [flashfs] found
found (1) 'aac.xexp' crc: 0x36790e61
found (2) 'bootanim.xex' crc: 0x187ede71
found (3) 'createprofile.xex' crc: 0x81d7a946
found (4) 'dash.xex' crc: 0x3957764c
found (5) 'deviceselector.xex' crc: 0x6246b4c0
found (6) 'gamerprofile.xex' crc: 0xb7add96a
found (7) 'hud.xex' crc: 0x202eb5c8
found (8) 'huduiskin.xex' crc: 0x4c80fbe9
found (9) 'mfgbootlauncher.xex' crc: 0x254ad664
found (10) 'minimediaplayer.xex' crc: 0xd8d21cfc
found (11) 'nomni.xexp' crc: 0xbf36fdf7
found (12) 'nomnifwk.xexp' crc: 0xa837ae53
found (13) 'nomnifwm.xexp' crc: 0x93246a8a
found (14) 'SegoeXbox-Light.xtt' crc: 0x086eb344
found (15) 'signin.xex' crc: 0xecd9cab1
found (16) 'updater.xex' crc: 0x125cdb94
found (17) 'vk.xex' crc: 0x9c744d4c
found (18) 'xam.xex' crc: 0x0b764b88
found (19) 'xenonclatin.xtt' crc: 0xd5d17ff5
found (20) 'xenonclatin.xttp' crc: 0x7a507ad1
found (21) 'xenonjklatin.xtt' crc: 0xdde4a14c
found (22) 'xenonjklatin.xttp' crc: 0x945b7092
found (23) 'ximecore.xex' crc: 0x8d45ea14
found (24) 'ximedic.xex' crc: 0x1d992bfb
found (25) 'ximedic.xexp' crc: 0xc90a651a
found (26) 'launch.xex' crc: 0x9f94f79b
found (27) 'lhelper.xex' crc: 0xeb581eb5
found (28) 'launch.ini' 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) 'secdata.bin' crc: 0x00000000
------ ini parsing completed ------
output name overridden to: nandflash.bin

------ Checking .\my360\nanddump.bin ------
Loading NAND dump (0x22eea0 bytes)...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 0x1c10c, 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 0x1c108, size 1536 (0x600) bytes
seeking security files...fsroot found at page 0x17ca0 raw offset 0x5c90a00
crl.bin found in sector 0x13a size 0x9e0...verified! Will use if external file not found.
extended.bin found in sector 0x34e size 0x4000...verified! Will use if external file not found.
secdata.bin found in sector 0x104 size 0x400...verified! Will use if external file not found.
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 .\14699\cb_6750.bin (0x9a40 bytes)
reading .\14699\cd_8453.bin (0x5780 bytes)
reading .\14699\ce_1888.bin (0x5606a b pad 0x56070 b)
reading .\my360\xell-gggggg.bin (0x40000 bytes)
reading .\14699\cf_14699.bin (0x4450 bytes)
reading .\14699\cg_14699.bin (0x67168 b pad 0x67170 b)
reading .\14699\bin\patches_fat.bin (0x6f0 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 for smc config data patches
smc config was not patched
---------------------
done!
------ Encrypting and finalizing bootloaders ------
SMC checksum: 5b3aed00
known clean SMC found, type: Jasper v4.1(2.03)
patching smc at offset: 0x12ba
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 none to 0x00011a40 len 0x0
adding cd_8453.bin to 0x00011a40 len 0x5a60
adding ce_1888.bin to 0x000174a0 len 0x56070
adding xell-gggggg.bin to 0x00070000 len 0x40000
adding cf_14699.bin to 0x000b0000 len 0x4450
adding cg_14699.bin to 0x000b4450 len 0x67170
adding patches_fat.bin to 0x000c0010 len 0x3e0
Writing CG patch slot overflow data to sysupdate.xexp1...done!
------ adding 28 firmware files ------
reading .\14699\aac.xexp (0x14000 bytes) (crc32: 0x36790e61 ini: 0x36790e61)
adding as aac.xexp1 at raw offset 0x2bdb5c0
reading .\14699\bootanim.xex (0x61000 bytes) (crc32: 0x187ede71 ini: 0x187ede71)
adding as bootanim.xex at raw offset 0x2bf0000
reading .\14699\createprofile.xex (0xc000 bytes) (crc32: 0x81d7a946 ini: 0x81d7a946)
adding as createprofile.xex at raw offset 0x2c51000
reading .\14699\dash.xex (0x63a000 bytes) (crc32: 0x3957764c ini: 0x3957764c)
adding as dash.xex at raw offset 0x2c60000
reading .\14699\deviceselector.xex (0x9000 bytes) (crc32: 0x6246b4c0 ini: 0x6246b4c0)
adding as deviceselector.xex at raw offset 0x329a000
reading .\14699\gamerprofile.xex (0x1b000 bytes) (crc32: 0xb7add96a ini: 0xb7add96a)
adding as gamerprofile.xex at raw offset 0x32a5000
reading .\14699\hud.xex (0x1e000 bytes) (crc32: 0x202eb5c8 ini: 0x202eb5c8)
adding as hud.xex at raw offset 0x32c3000
reading .\14699\huduiskin.xex (0x13000 bytes) (crc32: 0x4c80fbe9 ini: 0x4c80fbe9)
adding as huduiskin.xex at raw offset 0x32e2000
reading .\14699\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0x254ad664 ini: 0x254ad664)
adding as mfgbootlauncher.xex at raw offset 0x32f7000
reading .\14699\minimediaplayer.xex (0xc000 bytes) (crc32: 0xd8d21cfc ini: 0xd8d21cfc)
adding as minimediaplayer.xex at raw offset 0x3300000
reading .\14699\nomni.xexp (0xe000 bytes) (crc32: 0xbf36fdf7 ini: 0xbf36fdf7)
adding as nomni.xexp1 at raw offset 0x330c000
reading .\14699\nomnifwk.xexp (0x2000 bytes) (crc32: 0xa837ae53 ini: 0xa837ae53)
adding as nomnifwk.xexp1 at raw offset 0x331a000
reading .\14699\nomnifwm.xexp (0x5000 bytes) (crc32: 0x93246a8a ini: 0x93246a8a)
adding as nomnifwm.xexp1 at raw offset 0x331e000
reading .\14699\SegoeXbox-Light.xtt (0x6000 bytes) (crc32: 0x086eb344 ini: 0x086eb344)
adding as SegoeXbox-Light.xtt at raw offset 0x3325000
reading .\14699\signin.xex (0x16000 bytes) (crc32: 0xecd9cab1 ini: 0xecd9cab1)
adding as signin.xex at raw offset 0x332e000
reading .\14699\updater.xex (0x7000 bytes) (crc32: 0x125cdb94 ini: 0x125cdb94)
adding as updater.xex at raw offset 0x3346000
reading .\14699\vk.xex (0x9000 bytes) (crc32: 0x9c744d4c ini: 0x9c744d4c)
adding as vk.xex at raw offset 0x334f000
reading .\14699\xam.xex (0x236000 bytes) (crc32: 0x0b764b88 ini: 0x0b764b88)
adding as xam.xex at raw offset 0x3359000
reading .\14699\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
adding as xenonclatin.xtt at raw offset 0x3592000
reading .\14699\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
adding as xenonclatin.xttp1 at raw offset 0x36af000
reading .\14699\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
adding as xenonjklatin.xtt at raw offset 0x36c8000
reading .\14699\xenonjklatin.xttp (0x7000 bytes) (crc32: 0x945b7092 ini: 0x945b7092)
adding as xenonjklatin.xttp1 at raw offset 0x3870000
reading .\14699\ximecore.xex (0x15000 bytes) (crc32: 0x8d45ea14 ini: 0x8d45ea14)
adding as ximecore.xex at raw offset 0x3877000
reading .\14699\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
adding as ximedic.xex at raw offset 0x388d000
reading .\14699\ximedic.xexp (0x2800 bytes) (crc32: 0xc90a651a ini: 0xc90a651a)
adding as ximedic.xexp1 at raw offset 0x3920000
reading .\14699\launch.xex (0x9000 bytes) (crc32: 0x9f94f79b ini: 0x9f94f79b)
adding as launch.xex at raw offset 0x3922800
reading .\14699\lhelper.xex (0x6000 bytes) (crc32: 0xeb581eb5 ini: 0xeb581eb5)
adding as lhelper.xex at raw offset 0x392d000
reading .\14699\launch.ini (0x2e9 bytes)
adding as launch.ini at raw offset 0x3936000
------ adding 4 security files ------
reading .\my360\crl.bin (0xa00 bytes)
writing as crl.bin to flash
crl appears crypted, attempting to decrypt with CPU key...failed! Trying alternate key...success!
reading .\my360\dae.bin (0xad30 bytes)
writing as dae.bin to flash
dae appears encrypted, attempting to decrypt with CPU key...failed! Attempting to decrypt with alternate key...
success!
reading .\my360\extended.bin (0x4000 bytes)
writing as extended.bin to flash
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 ------
adding smc config to offset 0x03be0000, len 0x400
------ 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 image built, info:
---------------------------------------------------------------
Console : Jasper (big block)
NAND size: 64MiB (system only)
Build : Glitch
Xell : power on console with console eject button
CPU Key : 23==============111
1BL Key :
CF LDV : 3
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
 
Last edited:
  • Like
Reactions: grpracing

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
provided the KV hash check has been removed, the rebuilt NAND with the edited OSIG should work. However I stand by what I said - you shouldn't need to do it.

My Son had a benq, hitachi and a samsung drive in his Falcon JTAG and they ALL worked without any change to OSIG on either side.
 
  • Like
Reactions: grpracing

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
Ok, that is what we are trying to find out , martin. if i am then what is it? I have sent all the logs from cfw flashing and nand flashing so what is it that im missing? or what is it ive done wrong??? I am asking cause by all that ive read i have done everything i am supposed to.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
ok - to confirm:

Connect the drive to another console which has a samsung drive, flash with the same OFW and test it. Does it work?

If you can't do this, can you advise if this drive was 100% working before you started?
 
  • Like
Reactions: grpracing

grpracing

Junior Member
Jan 23, 2012
24
0
Misssissippi
yes, 2 of the 3 i have tested are 100% working.

We seem to be stuck on the drive as the issue, so this mean there couldnt be something wrong with the nand side? i have been told that there is problems with running the 13604 kernel. later today im gonna flash the 14699 kernel to it and see what happens.

I assure you all that i didnt post this thread to waste your time. i have done my homework and searching for over a week on any problem close to this and the few i have seen come up pointed towards the nand but i cannot find an error in the nand. hopefully an updated kernel does it.