Hacking Any ideas on how to progress when my Bis Keys say Keyblob corrupt?

[lpoolm]

So I have an old dead switch that was bought faulty a long time a go. It never had any shorts so have always thought it is a software issue?
I think it might be a firmware fuse miss match, have read you could try choidujoux on a pc but it doesn't work on the fuse count I am on.
I have tried a few basic things but not succeeded. have been able to back up the nand boot 0/1 though.
I got a copy of mattytrogs unbrick pack and thought would give this a go but straight off I try to get my Biskeys and get the below error.
Keyblob 0 - 5 corrupt. so straight off I am stuck, my knowledge on this is limited, can this be skipped? Is there any clever software out there that can rebuild from other files?
Any ideas to slowly progress me to the next step please.
Would love to get this switch going for my little girl while we are on lockdown!

 

[lpoolm]

Sorry to bump but still desperate for some external input please.

 

[LIY2012]

Sorry to bump but still desperate for some external input please.

What fuse count are you on?

Do you have a valid prodinfo?

Rebuilding the keyblobs is discussed in this thread here.
https://gbatemp.net/threads/keyblob-0-to-5-corrupted.548659/

 

[lpoolm]

What fuse count are you on?

Do you have a valid prodinfo?

Rebuilding the keyblobs is discussed in this thread here.
https://gbatemp.net/threads/keyblob-0-to-5-corrupted.548659/

I have 9 burnt fuses so should be on 7.0.0- 8.0.1.
I am not sure on the prodinfo and where to find it.
I think I have read through that thread but thanks for linking with give it another read now

 

[LIY2012]

I have 9 burnt fuses so should be on 7.0.0- 8.0.1.
I am not sure on the prodinfo and where to find it.
I think I have read through that thread but thanks for linking with give it another read now

Check your boot1 file in HxD and see what version it is.

It should say 20190208150037 for version 7.0.1 or 20190314172056 for 8.0.1

 

[lpoolm]

Check your boot1 file in HxD and see what version it is.
View attachment 208713

It should say 20190208150037 for version 7.0.1 or 20190314172056 for 8.0.1

Strange!
20180220163747

 

[LIY2012]

Strange!
20180220163747
View attachment 208717

That is the boot1 from firmware 5.1.0. That will not boot with your fuse count unless you use a loader such as hekate. Even then, it probably won't boot until you fix your keyblobs.

 

[lpoolm]

That is the boot1 from firmware 5.1.0. That will not boot with your fuse count unless you use a loader such as hekate. Even then, it probably won't boot until you fix your keyblobs.

Thanks for the input, I am attempting to try what is in that other thread to see what I can do.
New to this but love to learn!
At least I know what firmware I should be looking at now!

 

[LIY2012]

Thanks for the input, I am attempting to try what is in that other thread to see what I can do.
New to this but love to learn!
At least I know what firmware I should be looking at now!

No problem. It seems like it's either a firmware/fuse mismatch issue, or possibly a boot/firmware mismatch. If would recommend checking the firmware version using Firmware Version Inspector (google it) and see what you get. If It matches the boot, it should be as simple as fixing the keyblobs and launching through hekate. If it's 7 or 8, then updating the boot files to the proper version should be a simple fix.

Good luck.

 

[lpoolm]

No problem. It seems like it's either a firmware/fuse mismatch issue, or possibly a boot/firmware mismatch. If would recommend checking the firmware version using Firmware Version Inspector (google it) and see what you get. If It matches the boot, it should be as simple as fixing the keyblobs and launching through hekate. If it's 7 or 8, then updating the boot files to the proper version should be a simple fix.

Good luck.

Thanks again, you seem to know what you are talking about!
I hope you dont mind me messaging in the future if I need a little point in the right direction!

 

[LIY2012]

Thanks again, you seem to know what you are talking about!
I hope you dont mind me messaging in the future if I need a little point in the right direction!

No problem, I'm happy to help.