FIXED lost nanddump.bin and rgh2 not working - is rjtag possible?

jorden

Full Member
Nov 4, 2013
47
6
some time ago jrunner started to choose the windows temp folder as working folder. as it istn possible anymore to set the working wolder, i couldnt change that. today i dumped a jasper 16mb wrote the ecc and managed to close jrunner. the nanddump ist lost now. thx jrunner

my problem is that this bitch wont glitch at all. my question is, is it possible to rjtag the console with out nanddump? unfortuatly i just know that the console was updatet from 14719 to 16202. the ldv i dont know...
 
Last edited:

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
some time ago jrunner started to choose the windows temp folder as working folder. as it istn possible anymore to set the working wolder, i couldnt change that. today i dumped a jasper 16mb wrote the ecc and managed to close jrunner. the nanddump ist lost now. thx jrunner

my problem is that this bitch wont glitch at all. my question is, is it possible to rjtag the console with out nanddump? unfortuatly i just know that the console was updatet from 14719 to 16202. the ldv i dont know...
As long as you didnt dump any other nand after you dumped this one or delete the dumps manually, its still in jrunners working folder. But yes, R-jtag works on dashboard 16202.
 

jorden

Full Member
Nov 4, 2013
47
6
no, i didnt and its definitly not. maybe becouse its in the temo folder i searched c: for nanddump1.bin, but for nothing.....is there a chance to recover that file? o&o didnt helped out

if not:

how do i gonna have to proceed without nanddump after installing the r jtag?
 

BrockThunderjam

VIP Member
Jun 25, 2013
1,503
88
I believe the Xellous image is written to the first 50 blocks of the nand (like ecc), so you have two options. 1 - proceed with your rgh 2 install and try to get at least one good boot so you can grab your keys. 2 - uninstall and do rjtag to grab keys. Either way you will need to use the build nand without dump feature in jrunner to build your freeboot image.

If I were you I would do option 1.
 

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
no, i didnt and its definitly not. maybe becouse its in the temo folder i searched c: for nanddump1.bin, but for nothing.....is there a chance to recover that file? o&o didnt helped out

if not:

how do i gonna have to proceed without nanddump after installing the r jtag?
Did you create a ECC or did you flash one of the pre-compiled ones?
You can still recover your KV if you created one. Dump what you have on your nand and save it! The install the R-jtag, flash Xell for your console and boot it.
 

WildCard007

VIP Member
Feb 27, 2013
285
0
USA
Did you go to the actual folder or did you run a search? Open a folder and in the path bar type %temp% and hit enter, it will take you to the temp folder. And you can change the directory for the working folder in J-Runner. It's in the settings. Click the box next to Working Folder, select the directory you want to use, then click OK. It should change the directory to that. If not look in the section for J-Runner Official Support I know there is a solution in there.
 

jorden

Full Member
Nov 4, 2013
47
6
WHAAAAAT? yes baby i created an ecc (press on create ecc then write ecc) :D im dumping it right now.

i hope thats what you meant

can you tell me how to extract the kv from the dump i made, so i can check if the xbox stil booting orig dash

edit:

@wildcard i cant find the sttings tap in jr v2 :D


@brock i glitched a ton of boxes bot 5 hour are far to much :D


edit2:

http://team-xecuter.com/forums/showthread.php?t=92607
 
Last edited:

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
I hope you still have the original dump, I do not believe that the new xell images have the key vault injected into them, so if it doesnt show dvd key when you boot Xell and gives you KV_read errors and you dont have the original dump you made then i believe the key vault is lost, in which case stock will not work no matter what you do.

Also you will need the CPU key to inject the KV from the image on the console if the image even has it.so best bet would be to see if you can get rgh2 to boot xell. if it tells you the dvd key you are in the clear, if not you will have to inject a new KV or find the original dump(Better option) if it was deleted try an undelete program. as long as you know the first letter of the filename you should be able to undelete the file(Unless you have been saving a bunch of new files to your hdd, in which case the data may have been overwritten) Once you have the CPU key and nand dump i would recommend upgrading to R-JTAG as it boots faster(My rgh2 jasper would take up to 10 minutes some times to boot, R-Jtag always boots in under 30 sec, usually around 1-3 pulses. In freestyle in 30 sec.(Because of Fake Anim)
 
Last edited:

BrockThunderjam

VIP Member
Jun 25, 2013
1,503
88
I hope you still have the original dump, I do not believe that the new xell images have the key vault injected into them
If clicked "create ecc" it injects his kv into the ecc.

OP if your console is not booting in 5 hours I would start looking at your install, something isn't right. What does your setup look like? Can you post pics of your install?
 
Last edited:

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
WHAAAAAT? yes baby i created an ecc (press on create ecc then write ecc) :D im dumping it right now.

i hope thats what you meant

can you tell me how to extract the kv from the dump i made, so i can check if the xbox stil booting orig dash

edit:

@wildcard i cant find the sttings tap in jr v2 :D


@brock i glitched a ton of boxes bot 5 hour are far to much :D


edit2:

http://team-xecuter.com/forums/showthread.php?t=92607
what you wanna do is saving those dumps with the created ECC written to them, keep them safe!
the you need to get xell booting somehow, by RGH2 or R-jtag.
after that just follow this tutorial by Martin C:
http://team-xecuter.com/forums/archive/index.php/t-92607.html
 

jorden

Full Member
Nov 4, 2013
47
6
Guys i managed to get the cpu key with rgh 2.0 :D

my fuse txt:

fuseset 00: c0ffffffffffffff
fuseset 01: 0f0f0f0f0f0f0ff0
fuseset 02: 000000f00f0f0000

fuseset 07: fffffffffffff000
fuseset 08: 0000000000000000
fuseset 09: 0000000000000000
fuseset 10: 0000000000000000
fuseset 11: 0000000000000000
my ldv should be 13 and the cb version 12, right?


when i press create image without nanddump i get errors:

===================================================
Donnerstag, 21. November 2013 16:53:21

J-Runner v0.3 Beta (2) Started


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

Anyone offering hosting servers with unlimited speeds/traffic at good prices (or free :p), pm me on #J-Runner EFnet
Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Header is wrong..
Trinity
RGH2 Selected
Nand Initialization Finished
Initializing nanddump1.bin..
Header is wrong..
CpuKey is Correct
Added Key to Database
Extracting..
Saving SMC_en.bin
Saving SMC_dec.bin
Saving KV_en.bin
Saving KV_dec.bin
Saving smc_config.bin
Working...
Failed to find fcrt.bin
Trinity
Nand Initialization Finished
Extracting..
Saving SMC_en.bin
Saving SMC_dec.bin
Saving KV_en.bin
Saving KV_dec.bin
Saving smc_config.bin
Working...
Failed to find fcrt.bin
Retail Selected
Jasper 16MB Manually Selected
CpuKey is Correct
Load Files Initiliazation Finished
16537
Started Creation of the 16537 xebuild image
---------------------------------------------------------------
xeBuild v1.09.639
---------------------------------------------------------------
base path changed to C:\Users\x\Desktop\Xbox\JRunner\xeBuild
---- { Image Build Mode } ----
building retail 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: hacked or unknown SMC found? you should use a clean smc for a retail image!



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

jorden

Full Member
Nov 4, 2013
47
6
Retail Selected
Jasper 16MB Manually Selected
CpuKey is Correct
then im pressing on create image without nanddump an copying kv.bin smc.bin and smc_config.bin to the folder that pops up