RGH j runner program

[dayton1]

it will not boot all but it will boot into xell

---------- Post added at 10:19 ---------- Previous post was at 10:17 ----------

no i will get green light then 3red rings 0022 but it will boot into xell when i hit ject buttom

---------- Post added at 10:23 ---------- Previous post was at 10:19 ----------

you see in jrunner on right hand side patch is 0 6 and 7 and ldv 0 and pd is blank. normal its number in pd. what causes that missing smc???

 

[Martin C]

So it turns on?

What would shorting the NAND achieve?

the problem here is you haven't a clue what you're doing and are clutching at straws to get it working. Either get it to someone to sort or read through EVERYTHING until you understand what you're trying to achieve.

 

[dayton1]

you know anyone in usa that would fix it. i would seen it to them.

---------- Post added at 10:42 ---------- Previous post was at 10:42 ----------

it turns on

 

[Martin C]

So shorting the NAND would do nothing.

The problem is, and has always been, your RGH image. Either it's not writing back ok or (more than likely) your LDV is the problem.

What LDV do you have in your original NAND?

 

[dayton1]

set at 5 you can see it in the jrunner image in one of my post

---------- Post added at 10:52 ---------- Previous post was at 10:50 ----------

can i go back and change that number in mulit build till i get the right one all the way up to 80. i seen in one of your post it can go up to 80 ldv

 

[BL4K3Y]

You can get the LDV in XeLL, just combine the number of Fs on fuse-set lines 7 and 8.

Oh, and in that log you posted, I didn't see a CPU key.

Did you actually enter it or just edit it out in the post?

 

[Martin C]

set at 5 you can see it in the jrunner image in one of my post

---------- Post added at 10:52 ---------- Previous post was at 10:50 ----------

can i go back and change that number in mulit build till i get the right one all the way up to 80. i seen in one of your post it can go up to 80 ldv

I have a sticky right there in my sig called 'why is LDV important?'.

 

[dayton1]

i did line seven had 6 f's and line eight had no f's

---------- Post added at 10:57 ---------- Previous post was at 10:56 ----------

now i did do a update from 9919 to 1499 which i said in my early post

---------- Post added at 10:59 ---------- Previous post was at 10:57 ----------

i seen that that how i seen you said it can go up to 80

 

[Martin C]

But since you've seen yours is set to 6, that comment is irrelevent.

Get Multi_builder. Load your original NAND and CPU key into it.

Edit options.ini and change cfldv=6.

build a 14719 RETAIL image.

Load this new RETAIL image into J-Runner. Make sure LDV = 6.
Paste in your CPU key.
build an RGH image.
flash to your console.

 

[dayton1]

ok let me try that be back

 

[dayton1]

h

 

[Martin C]

1. Why select #1 when I said to create a RETAIL image?
2. Is this using your original NAND dump as the source? Can you upload it please?

 

[dayton1]

hi

 

[AMIT]

iam using orginal nand hold on

---------- Post added at 14:53 ---------- Previous post was at 14:43 ----------

samething happen. i select number 3 retail nand

xeBuild v1.00.356
---------------------------------------------------------------
building retail image
per build directory overridden from command line to 'my360'
data directory overridden from command line to '14699'
file name overridden from command line to 'retail_image.bin'

------ parsing user ini at '.\my360\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0x172 bytes in memory
loading cpukey.txt from .\my360\cpukey.txt
CPU Key set to: 0xCD206AF28C24F947D5F745E852C2FF37
setting 1blkey from ini: 0xDD88AD0C9ED669E7B56794FB68563EFA
1BL Key set to: 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)
xex Key set to: 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)

------ parsing ini at '.\14699\_retail.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) 'secdata.bin' crc: 0x00000000
------ ini parsing completed ------

output name overridden to: retail_image.bin


------ Checking .\my360\nanddump.bin ------
Loading NAND dump (0x28ee70 bytes)...done!
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!

fbbuild will attempt to keep this data, but
many things could cause it to be invalid/corrupt.
****************************************************

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

An unhandled exception 0xC0000005 has occured, exiting...

---------- Post added at 14:54 ---------- Previous post was at 14:53 ----------

any who in the us you think could look at at. iam in pontiac mich.

---------- Post added at 14:57 ---------- Previous post was at 14:54 ----------

its been comming up with that smc fail from the begining

gone to denist app be back 2 hours

As Martin C said ,can you please upload your nand ????

 

[dayton1]

ok sorry

 

[dayton1]

http:
trying how to do that whats the best way to load the bin file???

 

[dayton1]

http://www.2shared.com/file/7ZZTd8Ga/nanddump1.html

there you go

 

[axee44]

In first post you stated that you have 256MB nand yet your nanddump.bin is only 16MB??? Are you sure you read your nand properly?? If you have 256MB nand your nanddump.bin should be 64MB.

 

[Martin C]

How have you managed to screw this up when tools like J-Runner not only dump and compare the NAND for you, but also dump exactly what's needed (board type and NAND size is auto-detected).

I even have a roadmap for noobies to make sure you have the right NAND size dumped. It just goes to show that those who have problems are the ones who don't read..

Now's the time to send this to someone in the hope it can be salvaged.

 

[dayton1]

iknow
ive done three falcon no problem but jasper has differnt nands i look in system setting and got nand size wrong that nand size i think was not in the 200's. i paid a good price but no more.
at least i dont have soldering problem. but will read next time when something is new