Hacking hekate+ atmosphere problem with SXcore

[JaRocker]

Is there a tutorial how to generate boot ising EmmcHaccGen?

her you go,
put your firmware a folder and rename it to fw, it should be in the same location at EmmcHaccGen.exe along with your keys.txt if you have prod.keys change the line in the Command to mash what you have or you can just rename it to keys.txt,
after that's done you can cd to the location where you have all the files or just type cmd in your address bar in your Windows Explorer.
EmmcHaccGen --keys keys.txt --fw fw

 

[DPyro]

Where do you get firmware.

Nevermind I got it working. It didn't like my prod.keys.

Why are my bis keys different? Is this system specific?

 

[lyokohack]

I’m not sure what your asking for help with but if you need a easy cfw pack that comes with hekate you can use deepsea cfw pack https://github.com/Team-Neptune/DeepSea/releases/tag/v1.8.1
If you don’t want or need the extra stuff that comes with it just you the minimal version

thank you for this kit

because it is not me who made this hack

when i used this kit

I run "SysNAND (CFW)" the boot screen appears but this last crash

 

[JaRocker]

Where do you get firmware.

Nevermind I got it working. It didn't like my prod.keys.

Why are my bis keys different? Is this system specific?

Yes via keys are systems and can only be used on the system they com from,
Did you try renaming the prod.keys to keys.txt
You can get switch firmwares here.
:update I was told that I can’t post links to the switch firmware here so you’ll have to google it it should be hard to find

 

[Draxzelex]

Yes via keys are systems and can only be used on the system they com from,
Did you try renaming the prod.keys to keys.txt
You can get switch firmwares here.

You cannot link firmware files. Remove them before a moderator warns/bans you.

 

[JaRocker]

thank you for this kit

because it is not me who made this hack

when i used this kit

I run "SysNAND (CFW)" the boot screen appears but this last crash

Did you use the clean up open in the sx boot menu if not you have to use it everyone you power power down the switch otherwise you won’t be able to boot into atmosphere

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

You cannot link firmware files. Remove them before a moderator warns/bans you.

Ok thanks will do

 

[DPyro]

I got it working by finding a prod.keys online but how can I dump all the unique console keys and insert them into prod.keys? I was only able to find sd_seed and tsec_key.

I read you need to get all these keys
https://github.com/Thealexbarney/LibHac/blob/master/KEYS.md

 

[JaRocker]

I got it working by finding a prod.keys online but how can I dump all the unique console keys and insert them into prod.keys? I was only able to find sd_seed and tsec_key.

I read you need to get all these keys
https://github.com/Thealexbarney/LibHac/blob/master/KEYS.md

You only need your prod.keys/keys.txt
You don’t need your biskeys unless you’re planning on doing some kind of modification to the nand or trying to unbrick your switch if so here you go https://github.com/rajkosto/biskeydump. If not it’s not needed

 

[DPyro]

biskeydump doesn't work in sxos

 

[lyokohack]

Did you use the clean up open in the sx boot menu if not you have to use it everyone you power power down the switch otherwise you won’t be able to boot into atmosphere

thanks a lot for your support
I always use the funtion SXCORE clean up since you told me, my mistake is that I started it from hekate

here is my result now

[ERROR Fatal] error : [NXBOOT]kEY derivation failed!

Press POWER to reboot.

now it works but after this message , normal or not


after this message "Press POWER to reboot." the payload "fusee-primary" of the deep sea-minimal launcher and I think it works fine

 

[JaRocker]

biskeydump doesn't work in sxos

Sorry my bad slipped my mind here you go try this you hekate to dump the files needed
https://www.sdsetup.com/biskeygen

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

thanks a lot for your support
I always use the funtion SXCORE clean up since you told me, my mistake is that I started it from hekate

here is my result now

[ERROR Fatal] error : [NXBOOT]kEY derivation failed!

Press POWER to reboot.

now it works but after this message , normal or not


after this message "Press POWER to reboot." the payload "fusee-primary" of the deep sea-minimal launcher and I think it works fine

I’m not 100% sure of what you’re trying to say but you can’t use fusee-primary.bin even if you booting in from within hekate it’s not going to work

 

[lyokohack]

thank you for your part

don't you have an idea to solve this problem of boot message

 

[JaRocker]

thank you for your part

don't you have an idea to solve this problem of boot message

Yes I posted it in this thread just go back a bit that what I’ve been helping the other guy with you need to please the boot0 and boot1, I don’t think you need to do both maybe only boot0 but I did both

 

[Draxzelex]

Yes I posted it in this thread just go back a bit that what I’ve been helping the other guy with you need to please the boot0 and boot1, I don’t think you need to do both maybe only boot0 but I didn’t both

You need both BOOT0/BOOT1 if the firmware you are restoring is different than the current firmware as those two are firmware-specific.

 

[lyokohack]

Yes I posted it in this thread just go back a bit that what I’ve been helping the other guy with you need to please the boot0 and boot1, I don’t think you need to do both maybe only boot0 but I didn’t both

thank you

I have now seen your message, which I understood that it is about emunand already created ,
I haven't created my emunand yet, because I can't put it in my 32GB card, I can retrieve it with hekate, but I think I can't create it if the SD card can't put it in if that's the case

where I have to find these two BOOT0 / BOOT1 , in SXCORE or hekate, I don't know how it works or I have to put it in.

 

[JaRocker]

You need both BOOT0/BOOT1 if the firmware you are restoring is different than the current firmware as those two are firmware-specific.

Why would someone use a boo0/boot1 from a version other than the one they are only wouldn't that just give them a black screen on boot?

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

thank you

I have now seen your message, which I understood that it is about emunand already created ,
I haven't created my emunand yet, because I can't put it in my 32GB card, I can retrieve it with hekate, but I think I can't create it if the SD card can't put it in if that's the case

where I have to find these two BOOT0 / BOOT1 , in SXCORE or hekate, I don't know how it works or I have to put it in.

You can use backup boot0/boot1 use hekate or sx boot menu just look in under option you'll find them both

 

[lyokohack]

sorry for the delay because I have no connection at home during this time

I tried to restore the boots you told me about. atmosphere works but I still have this

[ERROR Fatal] error : [NXBOOT]kEY derivation failed![/INDENT]

Press POWER to reboot.

 

[Draxzelex]

Why would someone use a boo0/boot1 from a version other than the one they are only wouldn't that just give them a black screen on boot?

Because you were the one insisting that a person only needs BOOT0 which is false.

Yes I posted it in this thread just go back a bit that what I’ve been helping the other guy with you need to please the boot0 and boot1, I don’t think you need to do both maybe only boot0 but I didn’t both

 

[JaRocker]

Because you were the one insisting that a person only needs BOOT0 which is false.

Lolz you need to go bad a read before you Start accusing me of something I didn’t do If you went back he would see that was clearly a typo didn’t should’ve been did obviously

 

[Draxzelex]

Lolz you need to go bad a read before you Start accusing me of something I didn’t do I suggested that they may only need that not insisted on them only using it.

Its still bad advice and needs to be corrected before matters become worse. It doesn't matter what your intention was since what you said could brick the device.