RGH Fuse Calculator

[sthetix]

SOLVED Fuse Calculator

Hi, i just replaced a Corona XCGPU (the original XCGPU is dead - and I have to replace it, RGH it and alter its NAND)
after replacing, I got this from xell :

fuseset 00: c0ffffffffffffff
fuseset 01: 0f0f0f0f0f0ff0f0
fuseset 02: 0f00000000000000
fuseset 03: 1fe9c061e1bb8eaf
fuseset 04: 1fe9c061e1bb8eaf
fuseset 05: 39ca0776815c2889
fuseset 06: 39ca0776815c2889
fuseset 07: f000000000000000
fuseset 08: 0000000000000000
fuseset 09: 0000000000000000
fuseset 10: 0000000000000000
fuseset 11: 0000000000000000


Your CPU key : 1FE9C061E1BB8EAF39CA0776815C2889

What is the exact CB to use when using Fuse Calculator? I am confused about fuseset 02, it is printed 0F, which means 2? There is no "2" on Corona when using Fuse Calculator.
But I am now using CB 13181 and it boots fine to dashboard.
I am assuming that this XCGPU is taken from newer console that is in CB 13181 from the factory.


Thanks

 

[N.E.Modz]

Hi, i just replaced a Corona XCGPU, and I got this from xell :

fuseset 00: c0ffffffffffffff
fuseset 01: 0f0f0f0f0f0ff0f0
fuseset 02: 0f00000000000000
fuseset 03: 1fe9c061e1bb8eaf
fuseset 04: 1fe9c061e1bb8eaf
fuseset 05: 39ca0776815c2889
fuseset 06: 39ca0776815c2889
fuseset 07: f000000000000000
fuseset 08: 0000000000000000
fuseset 09: 0000000000000000
fuseset 10: 0000000000000000
fuseset 11: 0000000000000000


Your CPU key : 1FE9C061E1BB8EAF39CA0776815C2889

What is the exact CB to use when using Fuse Calculator? I am confused about fuseset 02, it is printed 0F, which means 2? There is no "2" on Corona when using Fuse Calculator.
But I am now using CB 13181 and it boots fine to dashboard.

Thanks

thats strange ? what dashboard are you on ?

 

[15432]

http://team-xecuter.com/forums/showthread.php?t=147046

read the last quote in OP

(so you need the dash ver <= 14699)

 

[sthetix]

This XCGPU wont boot xell if using CB 13121 or 13180, but it runs fine on CB 13181.
so at least it should be 15572 or later.

 

[15432]

This XCGPU wont boot xell if using CB 13121 or 13180, but it runs fine on CB 13181.

what? there is no XeLL image with CB 13180 or 13181.

Also, it's possible to disable fuses check at all with RGH, so... just make the retail image with CB 13121

 

[sthetix]

what? there is no XeLL image with CB 13180 or 13181.

Also, it's possible to disable fuses check at all with RGH, so... just make the retail image with CB 13121

Xell is displayable at CB 13181.
it is running fine on this console.
This console boots fine to dashboard (xebuild image).
I have altered its NAND and made several patches to match the console's serial number (which is printed on its labels) and its DVD key.

the only thing i am concerning is the fuseset 02.. when using Fuse Calculator

 

[sthetix]

canceled post..

 

[15432]

WTF? Everything I read here is just mess..................................

let's start from the beginning.
1. you need the fuse calculator ONLY to make the correct working retail image using RGH image with original, proper keyvault
1.1 if the keyvault was modified (dvdkey, serial, region, anything else) - retail image won't work
1.2 the keyvault is linked with CPU KEY. You can't use donor keyvault for retail image

2. You can't run RGH with the original CB because it has some anti-RGH checks
2.1 There's only one official patchset for coronas - for CB_B 13121. That loader was used in all freeboot & XeLL images
2.2 actually there is unofficial patchset for CB_B 13182, made by me, but let's skip it
2.3 so ... you couldn't run RGH with any of those 13180 and 13181 CB's. I think, you've just renamed the header, lol

3. When you use RGH2, you shouldn't care about fuses at all (except clean mfg cpu, but I've released solution for that case, too)
3.1 If you need to install freeboot, just make the image using donor decrypted files - place kv.bin, fcrt.bin, and other less important files in the data folder and press "build image without nanddump.bin"
3.2 actually, you can just build glitch2m image using ALL donor data, including cpu key - that image will work in any corona. but JRunner has that option disabled (dunno why). So you can try other builders

.........
if you still have questions, just post them here.
sincerely. 15432.

 

[sthetix]

WTF? Everything I read here is just mess..................................

let's start from the beginning.
1. you need the fuse calculator ONLY to make the correct working retail image using RGH image with original, proper keyvault
1.1 if the keyvault was modified (dvdkey, serial, region, anything else) - retail image won't work
1.2 the keyvault is linked with CPU KEY. You can't use donor keyvault for retail image

2. You can't run RGH with the original CB because it has some anti-RGH checks
2.1 There's only one official patchset for coronas - for CB_B 13121. That loader was used in all freeboot & XeLL images
2.2 actually there is unofficial patchset for CB_B 13182, made by me, but let's skip it
2.3 so ... you couldn't run RGH with any of those 13180 and 13181 CB's. I think, you've just renamed the header, lol

3. When you use RGH2, you shouldn't care about fuses at all (except clean mfg cpu, but I've released solution for that case, too)
3.1 If you need to install freeboot, just make the image using donor decrypted files - place kv.bin, fcrt.bin, and other less important files in the data folder and press "build image without nanddump.bin"
3.2 actually, you can just build glitch2m image using ALL donor data, including cpu key - that image will work in any corona. but JRunner has that option disabled (dunno why). So you can try other builders

.........
if you still have questions, just post them here.
sincerely. 15432.

yup!..sorry for the mess

case closed.

thx for the info !..

 

[15432]

finally.
4. each original dash has its own bootloaders
4.1 so if you want to make the retail image with 13121 bootloader, you have to build 14699 dashboard
4.2 to figure out what fuses does allow your bootloader, just open the build log, there is an interesting part:

CB 13182 seq 0x0304000e type: 0x03 cseq: 0x04 allow: 0x000e expected fuses:
fuseset 00: C0FFFFFFFFFFFFFF
fuseset 01: 0F0F0F0F0F0FF0F0
fuseset 02: 000F000000000000 (sequence)
fuseset 02: 0F00000000000000 (allow cseq 2)
fuseset 02: 00F0000000000000 (allow cseq 3)
fuseset 02: 000F000000000000 (allow cseq 4)

(that also means, corona CPU can be soldered on trinity mobo)

 

[BL4K3Y]

My fuse calculator works out which CB version and LDV a console needs to boot a retail NAND image.

Fuse line 2 tells you the CB version and fuse lines 7/8 tell you the LDV.

A retail/stock NAND will not boot if the KV or FCRT is invalid (FCRT only applies to slim consoles).

 

[15432]

My fuse calculator works out which CB version and LDV a console needs to boot a retail NAND image.

Fuse line 2 tells you the CB version and fuse lines 7/8 tell you the LDV.

A retail/stock NAND will not boot if the KV or FCRT is invalid (FCRT only applies to slim consoles).

Zephyrs have about 10 different CBs with many restrictions so sometimes it's impossible to find the right CB using only fuse 2 count. Total mess. If you need, I can post the full 02 fuse info. Or just forget it, anyway nobody cares about Zephyrs now.

 

[sthetix]

i just realize i made a mistake theoretically

:facepalm:​

and yes, we can swap any XCGPU with each others (trinity to corona and vice versa)
If you have a corresponding NAND chip (NAND info, like KV , etc) , you wont have to RGH it (as long as you have the correct CPU key)
Fuse Calculator is intended for retail NAND only to know exactly the CB and dashboard version accordingly.

Thanks to all for the replies and wake me up from daydreaming