RGH iam trying to rite image but fail

[dayton1]

is it because i did not update my xbox to a more newer update dash it was on dash 9199 iam getting this error from my nandflash.bin text doc this is whay it says:

xeBuild v1.01.421
---------------------------------------------------------------
building glitch image
data directory overridden from command line to 'xeBuild\14699'
per build directory overridden from command line to 'xeBuild\data'
file name overridden from command line to 'C:\Users\Owner\Documents\J RUNNER PROGRAM\320774584705\nandflash.bin'

------ parsing user ini at '.\xeBuild\data\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0x14f bytes in memory
loading cpukey.txt from C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\cpukey.txt
CPU Key set to: xxxxxxxxxxxxxxxxxxx
setting 1blkey from ini: xxxxxxxxxxx
1BL Key set to: xxxxxxxxxxsum: 0x983 (expects: 0x983)
xex Key set to: xxxxxxxx sum: 0x800 (expects: 0x800)
Using patchsmc option (ini file)

------ parsing ini at '.\xeBuild\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

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: C:\Users\Owner\Documents\J RUNNER PROGRAM\320774584705\nandflash.bin


------ Checking C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\nanddump.bin ------
Loading NAND dump (0x28ee70 bytes)...done!
Detecting NAND controller type from dump data...
NAND dump is from a big block machine
NAND dump uses big block controller
parsing dump into user and spare...


**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************

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 0xfc7a00! Using if no smc config is provided.
CF slot 0 decrypted ok LDV 0x05 Pairing: 0x7a9993
CF slot 1 decrypted ok LDV 0x04 Pairing: 0x7a9993
setting LDV from image to 5
setting pairing data from image to 0x7a9993
seeking security files...no valid FS root found!
Writing initial header to flash image

------ Loading bootloaders and required security files ------
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\smc.bin failed, using smc.bin from nand dump
reset smc load address to 0x1000 size 0x3000
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\kv.bin failed, using kv.bin from nand dump
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\14699\cb_6750.bin (0x9a40 bytes)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\14699\cd_8453.bin (0x5780 bytes)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\14699\ce_1888.bin (0x5606a b pad 0x56070 b)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\xell-gggggg.bin (0x40000 bytes)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\14699\cf_14699.bin (0x4450 bytes)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\14699\cg_14699.bin (0x67168 b pad 0x67170 b)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\14699\bin\patches_fat.bin (0x6f0 bytes)
reading C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\smc_config.bin failed, using smc_config.bin from nand dump
-------------------
checking smc_config
-------------------
******* ERROR: extracting config did not work, not enough data to copy!


**** could not read smc_config.bin (-2) ****

******* ERROR: critical bootloader files are missing, cannot proceed!



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

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

---------- Post added at 03:08 ---------- Previous post was at 03:07 ----------

i did not put my cpu key in there i erase with xxxxxxx

---------- Post added at 03:09 ---------- Previous post was at 03:08 ----------

i have jasper small block nand

 

[dayton1]

rgh hack also iam trying

 

[Netkar]

Recover your CPU key from xell with eject button, after rebuild image

 

[dayton1]

i have my cpu key already

---------- Post added at 03:34 ---------- Previous post was at 03:33 ----------

i did all that wont make nandflash.bin fail to rite see in log

 

[bmonster007]

Not sure if this has anthing to do with it, you say yours is a Jasper Small Block, but it looks like in the log its being detected as a big block.

------ Checking C:\Users\Owner\Documents\J RUNNER PROGRAM\xeBuild\.\xeBuild\data\nanddump.bin ------
Loading NAND dump (0x28ee70 bytes)...done!
Detecting NAND controller type from dump data...
NAND dump is from a big block machine
NAND dump uses big block controller
parsing dump into user and spare...

 

[legitmod]

as of right now you can't RGH phat consoles on the new dash 14719

 

[Argentum]

as of right now you can't RGH phat consoles on the new dash 14719

He said his dash is 9199 so he is fine with that


Let's get it from the start did you check your nand dump?

If it is fine. flash back your original nand .... update to 14699 then take a new dump as the LDV value will be changed

Then check the new dump and enter your cpukey then creat the image

 

[Ir0nman]

Your smc_config.bin is not being extracted properly by the software. This can easily be fixed by using donor files. Is your nanddumps 66MB or 16MB? You either have an incomplete dump or a bad dump.

 

[dayton1]

sorry let my computer on fell asleep going to get up.got to go smmewhere this morning back later t0 finish

 

[dayton1]

can someone tell me what i did wrong

 

[dayton1]

it wont turn on now so i guess trash can time

 

[Evil0ne]

it wont turn on now so i guess trash can time

no.... not trash can time, how about u read what we've said, also have u tried using j-runner vs xebuild?
if its not powering on its cause the smc is messed up and its fixable, u just have to b willing to work for it, there's 2 methods on involved bridging 2 points, the other involves plugging in the Xbox in and IMMEDIATELY writing the ecc
within the first .2 .3 seconds and timeing is critical on that one but the box is by no means "trash can" time

 

[Argentum]

He said his dash is 9199 so he is fine with that


Let's get it from the start did you check your nand dump?

If it is fine. flash back your original nand .... update to 14699 then take a new dump as the LDV value will be changed

Then check the new dump and enter your cpukey then creat the image

Did you try this yet?

 

[dayton1]

evilone what are the two bridge points i can get it back up running. i know before it quit turning on the fan got read loud then it went off. i think when i wrote the nand i thought it was a small block nand but it was a regular 16mb jasper nand not the 256 or 512 nand also. what is the difference size to see in setting to know i have a small block nand or a regular 16mb nand. i did wrote back the nand but now it wont turn on.i just want to get it back to orginal so i can sell it as orginal nand no hack thanks.

---------- Post added at 06:24 ---------- Previous post was at 06:19 ----------

i think i got mess between small block and regular block nand first wrote it as small block nand. i wrote 256 and 512 nands and went find just this.

 

[dayton1]

ive read up on big block has a 256 =214. 512=451 cap and 16mb nand has no memory unit. value was so low thats why i chose small block nand.

---------- Post added at 06:36 ---------- Previous post was at 06:35 ----------

i did a search but not for small block i could not find

 

[dayton1]

i got it writing to nand but it running real slow. is that normal when nand it mess up. it say flash config : ox008a3020
orginal code say 16 mb flash code is 00023010

 

[dayton1]

when it writing its showing just 2 parts rather than 3. example: d8,d9 da,db dc, so it must have wrote as small block nand

 

[dayton1]

its showing 3 digits now i guess it too a while to get there