check my nand pls

[BrockThunderjam]

I'm not seeing any confusion at all. Not sure what you're getting at.

You're right. I'm going to go sit in the corner for a while.

 

[b3datarin]

When it comes to RGH2, the NAND is completely irrelevant. I'm not sure why you keep asking me to check it.

ok . so can i erase all data on nand and then write ECC ( just for knowledge )
i think my RGH2.0 wiring is not good enough . test it tomorrow ( day that my international team play with leo messi team:tongue: . )
and will report .
thanks alot dear jsinger47

 

[Taijigamer2]

No need to erase. Just write ecc. It will over write the current ecc ( first 50 blocks of nand) or whatever the last guy put on there :-/

 

[b3datarin]

RGH2.0 completed and i got cpukey .
thanks alot .
extracted nand and got
SMC_dec
SMC_en ---------------> SMC.bin
SMC Config------------->SMC_config.bin
KV_en------------------>KV.bin

and copied that to data folder on the xebuild folder .

when i start to create an image without nanddump ( retail ) i have :

===================================================
Saturday, June 21, 2014 2:44:43 PM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Wrong CpuKey
Jasper 16MB Manually Selected
Load Files Initiliazation Finished
16747
Started Creation of the 16747 xebuild image
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to D:\JR\xeBuild
---- { Image Build Mode } ----
building retail image




******* ERROR: hacked or unknown SMC binary found? you should use a clean SMC binary for a retail image!






***** FATAL BUILD ERROR: -4 unable to complete NAND image


---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Failed

also this for RGH2 image :

===================================================
Saturday, June 21, 2014 2:58:32 PM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Wrong CpuKey
Connection Error
Checking Files
RGH2 Selected
Jasper 16MB Manually Selected
Load Files Initiliazation Finished
16747
Started Creation of the 16747 xebuild image
Connection Error
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to D:\JR\xeBuild
---- { Image Build Mode } ----
building glitch2 image




******* ERROR: could not decrypt keyvault, please be sure your provided a valid kv.bin!




***** 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




***** ERROR: -2 writing to file D:\JR\ \updflash.bin


---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Failed

i am sure that cpukey is correct . double checked .
can you create image for me ?
i give to you cpukey .

:frown:

 

[simlol]

you cant use enc's..you must use the dec's file..beacause they are donor files..

 

[b3datarin]

you cant use enc's..you must use the dec's file..beacause they are donor files..

used dec's SMC file. same result .

 

[simlol]

used dec's SMC file. same result .

you cant build retail image..

 

[b3datarin]

RGH 2.0 . same result . i can give cpukey to you .can you make it for me ?

===================================================
Saturday, June 21, 2014 5:13:21 PM


J-Runner v0.3 Beta (4) Started






Checking Files
Finished Checking Files
Initializing 2.bin..
Header is wrong..
Wrong CpuKey
Jasper 16MB
Jtag Selected
Nand Initialization Finished
Extracting..
Saving SMC_en.bin
Saving SMC_dec.bin
Saving KV_en.bin
Saving KV_dec.bin
Saving smc_config.bin
Finished
RGH Selected
RGH2 Selected
Wrong CpuKey
Load Files Initiliazation Finished
16747
Started Creation of the 16747 xebuild image
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to D:\JR\xeBuild
---- { Image Build Mode } ----
building glitch2 image


***** WARNING: ignoring possible remap of block 0x1 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x5 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x6 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x7 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x8 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x9 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0xa to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0xb to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0xc to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0xd to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0xe to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0xf to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x10 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x11 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x12 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x13 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x14 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x15 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x16 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x17 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x18 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x19 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x1a to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x1b to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x1c to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x1d to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x1e to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x1f to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x20 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x21 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x22 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x23 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x24 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x25 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x26 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x27 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x28 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x29 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2a to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2b to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2c to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2d to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2e to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x2f to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x30 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x31 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x32 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x33 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x34 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x35 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x36 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x37 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x38 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x39 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3a to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3b to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3c to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3d to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3e to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x3f to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x40 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x41 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x42 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x43 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x44 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x45 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x46 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x47 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x48 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x49 to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4a to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4b to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4c to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4d to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4e to block 0x0
this dump may have some bad data!
***** WARNING: ignoring possible remap of block 0x4f to block 0x0
this dump may have some bad data!
***** WARNING: could not find a non-zero CF LDV to use, setting it to 1 but that may be incorrect!


******* ERROR: could not decrypt keyvault, please be sure your provided a valid kv.bin!




***** 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




***** ERROR: -2 writing to file D:\JR\ \updflash.bin


---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Failed

 

[simlol]

just extract dec's files of kv,smc,smc_config from another donor jasper put them in data folder...put cpukey then create image without nanddump,put ldv value,end of story.

 

[b3datarin]

for dec's KV.bin cpukey needed .
can i use my last jasper that have been glitched ?

 

[b3datarin]

Thanks to everyone that helped me .
you are real MASTERS .
with dec's SMC & SMC_CONFIG & KV frome another jasper and cpukey console i could make RGH2.0 image .
console boot fine NOW .
+rep to all my friend .

 

[b3datarin]

can someone say me why console usb ports didn't work ?
is this for nand file related or SMC ? ????
also i did flashed lt3.0 fw with dvdkey i catched from xell . and dvd drive can not play game.

 

[unkn0wn.92]

can someone say me why console usb ports didn't work ?
is this for nand file related or SMC ? ????
also i did flashed lt3.0 fw with dvdkey i catched from xell . and dvd drive can not play game.

for USB ports is all of your ports not working ?
and for LT3.0 what did you get ? and try to enable no_Fcrt patch and rewrite the glitched image

 

[b3datarin]

usb ports worked. my mistake .
but i have Play DVD .
try to create cfw with dvdkey than shown on Xell .
but didnt work .
FCRT.bin for 162ds ???
you sure?

 

[AllyNerd]

usb ports worked. my mistake .
but i have Play DVD .
try to create cfw with dvdkey than shown on Xell .
but didnt work .
FCRT.bin for 162ds ???
you sure?

What's the osig and is that the original drive that came with the console? I didn't notice your jungle flasher log can you post it?

 

[b3datarin]

What's the osig and is that the original drive that came with the console? I didn't notice your jungle flasher log can you post it?

used another Dec's file for create nandflash .
and new dvdkey from kv.bin
problem solved .
tnx