RGH Two concerns about a NAND

[oblivioncth]

I am building a donor NAND for a Trinity with RGH 1 that is believed to have last been on 14699. Also the only NAND dump available is from Fusion so there is no fcrt.bin

This is what I have done:
1)Loaded in CPU key
2)Enabled no fcrt.bin patch
3)Set dash to 14699, set the bubble to glitch, and the glitch drop down to RGH
4)Set the console type to Trinity
5)Placed kv_dec.bin, smc_dec.bin, and smc_config as KV.bin, SMC.bin, and smc_config.bin in the data folder of xebuild
6)Renamed a .txt file to fcrt.bin to make a dummy since J-Runner doesn't let you continue without it
7)Selected "Create an image without nanddump.bin"
8)Set LDV to 10 (known from fusesets in xell) and clicked OK

It created an image but there are two concerns I have:

1) After making the image J-Runner gave this error:

I am assuming that this is just because fcrt.bin isn't real so this is nothing to worry about. The log did give an error about fcrt.bin which is expected.

2) At the end of the log it says the KV type is "1 (no hash)". Is this something that Fusion did, because I know for sure that nothing but Xenons use type 1?

Is the dump that was generated OK to try or do I need to worry about the above or anything else?

Thanks.

 

[stefanounick]

nvm the error

as for the kv shouldnt be type 1, thats weird

 

[oblivioncth]

nvm the error

as for the kv shouldnt be type 1, thats weird

Ya I thought the error was ok, it is the KV that bothered me.

I can upload the files if you or anyone wants, but its not like anything can really be done lol

I guess I just have to go for it.

 

[madhaxer]

First there is no rgh1 on slim consoles, as they all are split cb's, second it should be a type 2 (hashed) kv what has happened is fusion is a program made from files pulled out of a dev kit console that had a type 1 kv, if you have ever installed it on say a rgh 2 console on 14719 dash, you could check your dash kernal and it shows a 13*** dash kernal, it is the fusion program, not sure if the Trinity will boot with a type1 kv, have never tried it my self.

 

[oblivioncth]

First there is no rgh1 on slim consoles, as they all are split cb's, second it should be a type 2 (hashed) kv what has happened is fusion is a program made from files pulled out of a dev kit console that had a type 1 kv, if you have ever installed it on say a rgh 2 console on 14719 dash, you could check your dash kernal and it shows a 13*** dash kernal, it is the fusion program, not sure if the Trinity will boot with a type1 kv, have never tried it my self.

Lol yea I always say RGH 1 for slims, don't know why.

Well I guess I just have to see how it goes.

 

[madhaxer]

Save your fusion nand dump so if nothing else you can always go back to fusion, if it don't work out for you.

 

[oblivioncth]

If anyone is wondering, the user got his original NAND from the seller so I don't know if the type 1 KV would work.