Hacking Biskeys...

Aymenmoham

Member
OP
Newcomer
Joined
May 8, 2019
Messages
22
Trophies
0
Age
29
XP
188
Country
Saudi Arabia
Hello everyone
My problem start when I downgrade from 8.0.1 to 4.1.0, I can't boot either cfw or ofw, in reinx it's gives package2 magic invalid,
In hekate read pkg2 failed,

Now I trying to build new nand, I flashed boot0 and boot1, after that in hacmountdisk step in prodinfo its shows fail! Entropy.
 

Attachments

  • IMG-20190520-WA0003.jpeg
    IMG-20190520-WA0003.jpeg
    1.7 MB · Views: 269
  • IMG-20190520-WA0002.jpg
    IMG-20190520-WA0002.jpg
    62 KB · Views: 208
  • IMG-20190520-WA0001.jpg
    IMG-20190520-WA0001.jpg
    27.8 KB · Views: 240
  • IMG-20190520-WA0000.jpg
    IMG-20190520-WA0000.jpg
    51.9 KB · Views: 202

mattytrog

You don`t want to listen to anything I say.
Member
Joined
Apr 27, 2018
Messages
3,708
Trophies
0
Age
48
XP
4,328
Country
United Kingdom
Hello everyone
My problem start when I downgrade from 8.0.1 to 4.1.0, I can't boot either cfw or ofw, in reinx it's gives package2 magic invalid,
In hekate read pkg2 failed,

Now I trying to build new nand, I flashed boot0 and boot1, after that in hacmountdisk step in prodinfo its shows fail! Entropy.
1) Check your keyblobs are intact. Try using Lockpick or my hekate mod to see if you can derive keys. It will probably fail on some, but we need to see if your keyblob data is valid.

2) Next... We need to get rid of any packages from SYSTEM/save. Get rid of all apart from 8000000000000120. If savemeta exists... Delete all apart from the savemeta to the 120 file.

3) Get your "clean" boot0(and boot1) for your desired firmware

4) Flash these cut-down BOOT0/1. They must be 1536kb in size(boot0) and 512kb(boot1). DO NOT FLASH ANY 4096kb size files. This will destroy your keyblobs

5) Boot with Atmosphere (fusee-primary). A full installation of atmosphere(with sigpatches etc)

Good luck.
 

Philliyxx

Well-Known Member
Member
Joined
Sep 21, 2018
Messages
304
Trophies
0
Age
36
XP
943
Country
United States
1) Check your keyblobs are intact. Try using Lockpick or my hekate mod to see if you can derive keys.

4) Flash these cut-down BOOT0/1. They must be 1536kb in size(boot0) and 512kb(boot1). DO NOT FLASH ANY 4096kb size files. This will destroy your keyblobs

Do you need keyblobs post 6.2? If they are corrupted can you recover them? If you can't what happens?
 

Aymenmoham

Member
OP
Newcomer
Joined
May 8, 2019
Messages
22
Trophies
0
Age
29
XP
188
Country
Saudi Arabia
1) Check your keyblobs are intact. Try using Lockpick or my hekate mod to see if you can derive keys. It will probably fail on some, but we need to see if your keyblob data is valid.

2) Next... We need to get rid of any packages from SYSTEM/save. Get rid of all apart from 8000000000000120. If savemeta exists... Delete all apart from the savemeta to the 120 file.

3) Get your "clean" boot0(and boot1) for your desired firmware

4) Flash these cut-down BOOT0/1. They must be 1536kb in size(boot0) and 512kb(boot1). DO NOT FLASH ANY 4096kb size files. This will destroy your keyblobs

5) Boot with Atmosphere (fusee-primary). A full installation of atmosphere(with sigpatches etc)

Good luck.
I uploaded some pictures
 

mattytrog

You don`t want to listen to anything I say.
Member
Joined
Apr 27, 2018
Messages
3,708
Trophies
0
Age
48
XP
4,328
Country
United Kingdom
Do you need keyblobs post 6.2? If they are corrupted can you recover them? If you can't what happens?
They shouldn't be. They will only be destroyed if you have written over them with a full 4096kb

--------------------- MERGED ---------------------------

Upload repair main, repair sub. prodinfo and prodinfof somewhere as well as your bis keys... I'll build you a new rawnand
 
  • Like
Reactions: LDGerald23

mattytrog

You don`t want to listen to anything I say.
Member
Joined
Apr 27, 2018
Messages
3,708
Trophies
0
Age
48
XP
4,328
Country
United Kingdom
Your system could not derive the keys... I don`t think its an issue though because it is just PKG2 thats failing.

I`ve had systems booting (with AMS) where the keyblobs were missing. So don`t panic!
 

mattytrog

You don`t want to listen to anything I say.
Member
Joined
Apr 27, 2018
Messages
3,708
Trophies
0
Age
48
XP
4,328
Country
United Kingdom
keyblobs are not used on 6.2.0+ and are not required for the system to boot. If they get messed up and you need them, it is possible to recover them
The OP is on 4.1.

Very doubtful they are messed up though, unless he has restored a backup from another console.

I think its just a matter of fixing his boot0 and booting with AMS

Sorry @Philliyxx thought you were the OP... :)
 
D

Deleted User

Guest
well guess you dont have a nand backup so it will be hard. im really not good at booting the sys but try what mattytrog says.
 

LDGerald23

New Member
Newbie
Joined
Jun 29, 2019
Messages
2
Trophies
0
Age
36
XP
48
Country
Mexico
They shouldn't be. They will only be destroyed if you have written over them with a full 4096kb

--------------------- MERGED ---------------------------

Upload repair main, repair sub. prodinfo and prodinfof somewhere as well as your bis keys... I'll build you a new rawnand

i had the same problem, my biskeys are not working correctly biskey 2 and 3 from save and system gives me fail entropy, i can not acces them, the switch that sent me only enters to RCM, no switch logo, no OFW or CFW, can you help me?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Guillotine