Hi to all i have a problem with prodinfo with hackdiskmount i have all my key but when i have to enter the biskey 00 for prodinfo i become (FAIL Entropy: 7.989 (tested 16384 out of 16834 Bytes) what is the problem the bis key i have are not working or what that mine?
- Thread starter Alschepmist
- Start date
- Views 4,592
- Replies 17
Sorry for that.
I try to downgrade from 8.1.0 to 6.1.0 and i use a tutorial i have dumped my key with hekate TSEC Keys dump and dump key fuse and i retrieved my bisskey key with online bisskeygen but hackdiskmount tell me fail are problem with hackdisk mount and windows 10?
I try to downgrade from 8.1.0 to 6.1.0 and i use a tutorial i have dumped my key with hekate TSEC Keys dump and dump key fuse and i retrieved my bisskey key with online bisskeygen but hackdiskmount tell me fail are problem with hackdisk mount and windows 10?
Okay, before I start thinking about your problem: Did you update the console from 6.1.0 to a higher version with ChoiDojourNX? Because if you update on the official way, there is no way to downgrade because you have burnt fuses.
Fuses burnt are 10 so no way to downgrade ? How about neue installation of the firmware with ChoiDojour but there are not compatible with 8.1.0 or ?
Did you not backup your biskeys on day 1 ? on your very first backup ?
anyhow
restore most earliest Nand backup, or working rawnand/image with hekate..
Make sure it boots with hekate..
Then once into the system run choidujourNx with latest system version files on sd you wish to install..
Or use choidujour.exe and rebuild yourself a new image.
If you pulled biskeys from that console, and console was working when pulled then they are the biskeys for that system and are working. The biskeys do not change on there own.
Try use the biskeys against your old backup and see if it passes...
Start again budd from the very first backup of system you ever did and build on that.
Ignore fuses and versions, as if you boot with hekate it should boot them all.
Ask @mattytrog Nicely and im sure he can fix ya prodinfo issue...
Something you did is corrupt and it wont match..with ya biskeys.
anyhow
restore most earliest Nand backup, or working rawnand/image with hekate..
Make sure it boots with hekate..
Then once into the system run choidujourNx with latest system version files on sd you wish to install..
Or use choidujour.exe and rebuild yourself a new image.
If you pulled biskeys from that console, and console was working when pulled then they are the biskeys for that system and are working. The biskeys do not change on there own.
Try use the biskeys against your old backup and see if it passes...
Start again budd from the very first backup of system you ever did and build on that.
Ignore fuses and versions, as if you boot with hekate it should boot them all.
Ask @mattytrog Nicely and im sure he can fix ya prodinfo issue...
Something you did is corrupt and it wont match..with ya biskeys.
Last edited by Canna,
Actually scratch what I said before, it's not compatible with 8.1.0.
But the guy who said you can't downgrade is wrong. It's just that you will need to boot a payload through RCM mode to disable fuse checks, it won't boot normally.
I also haven't done the BIS key backup on day one and have derived them using the tutorial. Unfortunately even though I've tried several times the BIS keys I think are courrupted in the NAND and just don't match. I have a NAND backup from hekate on firmware 4.0.1, but when I tried to go back from 6.0.1 to 4.0.1 (for a clean start), I didn't realize that the switch had already burnt those fuses even though I used ChoidujourNX. Anyways, the situation is just not good at all.
I wanted to build on my previous NAND backup, but I can't due to the BIS keys! At least to boot into an OFW as I've burned 7 fuses so far and I'm stuck on my restore of 4.0.1.
Last edited by hell_night,
You can restore any backup of nand with Hekate and it will boot, Hekate bypasses fuse check... Restore 4.1 With hekate/Dont forget to restore the boot0 and boot1 as they must be restored also, boot0 and boot1 must much the fw you are putting on the console... Once you restore 4.1 and the boot0/1 files for 4.1 then you launch hekate again and run your cfw, Or sxos.. Once your back in system use homebrew app choidujourNX and upgrade to 6.0.1 if thats what you want.. any fw or fuse version below the current fuse count will not boot without hekate, or a fuse check bypass.
Dont be messing with your 4.1 nand image you corrupt that your fckd. With out the correct biskeys..
Last edited by Canna,
I really appreciate you taking the time to write all this for someone you barely know. I understand the gravest mistake I've done due to having two separate systems. The worst mistake I've ever done was yesterday in the console scene in general... I guess everyone makes mistakes once in a blue moon... or just unlucky...
I'm sure if I had followed your method and the method I was following on the Internet things would've booted.. But oh well I'm left with a paperweight as I flashed the wrong NAND... My noobiest mistake of all time..
Hey if your still having this issue try rebuilding your nand if you can get your prod.keys just got mine fixed had an issue with my prodinfof https://suchmememanyskill.github.io/guides/unbrick/ let me know if it helps
Similar threads
- No one is chatting at the moment.
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
