Hacking Question Can´t start CFW or OFW on switch after 9.0.0 update

[Don328]

Hey Guys,
i updated my switch two weeks ago with os sx 2.9 beta to 9.0.0.
Of course i had the freeze during the installation of 9.0.0 too.
so i waited for an update from xecuter team and now there is sx os 2.9.2 beta.
i updated the sx os and now i am on 2.9.2 and wanted to upgrade or downgrade my firmware so i can play again with my switch.
But no chance. i can´t start nothing.
-the ofw is not starting
- i can boot into sx os but when i click on start cfw i get a black screen and nothing happens

i also tried atmosphere but there i also get an black screen after it starts.

i dont know what to do. can someone please help with my problem?

 

[Taorn]

Do you have an backup of your nand from when it was working? If yes, then restore it with Hekate.

If not then you're probably stuck to building a new nand with ChoiDujour. Yes, not NX. If you decide to do that:

• Backup your current damaged nand
• Dump your keys
• Do a good amount of research BEFORE beginning

Don't follow the first youtube tutorial you find. Don't follow any of them.

 

[Don328]

never done this before. but how can i run choidujour. i cant start shit with my broken switch :/

is there any other way? this looks complicated af.
many people screwed there switch by updating with 2.9.

how did they fix the problem?

 

[Taorn]

never done this before. but how can i run choidujour. i cant start shit with my broken switch :/

is there any other way? this looks complicated af.
many people screwed there switch by updating with 2.9.

how did they fix the problem?

Afaik the only way to recover from this is as described. Sorry, there is no easy fix for this. An even more detailed guide can be found here: https://switch.homebrew.guide/usingcfw/manualchoiupgrade
Read it carefully before you begin.

More information can be found here: https://gbatemp.net/threads/warning...ack-screen-after-9-0-0-update-attempt.549146/.

 

[Don328]

Afaik the only way to recover from this is as described. Sorry, there is no easy fix for this. An even more detailed guide can be found here: https://switch.homebrew.guide/usingcfw/manualchoiupgrade
Read it carefully before you begin.

More information can be found here: https://gbatemp.net/threads/warning...ack-screen-after-9-0-0-update-attempt.549146/.

I have tried to follow the guide. but when i try to run the cmd at step 4.3 i get an error

Spoiler

\Choidujour>ChoiDujour.exe --keyset=keys.txt fw

ChoiDujour 1.1.0 by rajkosto
uses hactool by SciresM (https://github.com/SciresM/hactool)
visit https://switchtools.sshnuke.net for updates and more Switch stuff!

Using source firmware files from folder fw
Traceback (most recent call last):
File "ChoiDujour.py", line 517, in <module>
File "ChoiDujour.py", line 225, in call_hactool
Exception: [WARN]: Failed to match key "bis_kek_source", (value "34c1a0c48258f8b4fa9e5e6adafc7e4f")
[WARN]: Failed to match key "bis_key_00", (value "986e45f6bafffed198d57f8ac4a60660b028f3b54f287859d2f2dd46ff8e728d")
[WARN]: Failed to match key "bis_key_01", (value "00c5e3ee589145c2eb7a1c35c3565f638717b2d1b93a87a792b2daca3cafaba9")
[WARN]: Failed to match key "bis_key_02", (value "46ae2132d2b6e51e42e7186fe5997385a8e7e206b257b199dfcddc77ba2e1eb0")
[WARN]: Failed to match key "bis_key_03", (value "46ae2132d2b6e51e42e7186fe5997385a8e7e206b257b199dfcddc77ba2e1eb0")
[WARN]: Failed to match key "bis_key_source_00", (value "f83f386e2cd2ca32a89ab9aa29bfc7487d92b03aa8bfdee1a74c3b6e35cb7106")
[WARN]: Failed to match key "bis_key_source_01", (value "41003049ddccc065647a7eb41eed9c5f44424edab49dfcd98777249adc9f7ca4")
[WARN]: Failed to match key "bis_key_source_02", (value "52c2e9eb09e3ee2932a10c1fb6a0926c4d12e14b2a474c1c09cb0359f015f4e4")
[WARN]: Failed to match key "device_key", (value "9f739c7a76cceb8b4deed83b2f885145")
[WARN]: Failed to match key "master_kek_00", (value "f759024f8199101dddc1ef91e6eecf37")
[WARN]: Failed to match key "master_kek_01", (value "bd27264ae07e979756411d0c66e679e3")
[WARN]: Failed to match key "master_kek_02", (value "a3d4a8e153b8e6ae6e6aef3e8f219cb4")
[WARN]: Failed to match key "master_kek_03", (value "1558f525ae8c5be9243fb6d8a8b0a8ee")
[WARN]: Failed to match key "master_kek_04", (value "9fbeb1957fc1629e08b753a9086d6e01")
[WARN]: Failed to match key "master_kek_05", (value "94a92da1d73c2b3e165c891ced5607fc")
[WARN]: Failed to match key "master_kek_06", (value "a6c7b7870e42d5302fe6110883aa3889")
[WARN]: Failed to match key "master_kek_source_06", (value "294c04c8eb10ed9d516497fbf34d50dd")
[WARN]: Failed to match key "master_kek_source_07", (value "decfebeb10ae74d8ad7cf49e62e0e872")
[WARN]: Failed to match key "master_kek_source_08", (value "0a0ddf3422066ca4e6b1ec7185ca4e07")
[WARN]: Failed to match key "master_kek_source_09", (value "6e7d2dc30f59c8fa87a82ed5895ef3e9")
[WARN]: Failed to match key "per_console_key_source", (value "4f025f0eb66d110edc327d4186c2f478")
[WARN]: Failed to match key "retail_specific_aes_key_source", (value "e2d6b87a119cb880e822888a46fba195")
[WARN]: Failed to match key "rsa_oaep_kek_generation_source", (value "a8ca938434127fda82cc1aa5e807b112")
[WARN]: Failed to match key "rsa_private_kek_generation_source", (value "ef2cb61a56729b9157c38b9316784ddd")
[WARN]: Failed to match key "save_mac_kek_source", (value "d89c236ec9124e43c82b038743f9cf1b")
[WARN]: Failed to match key "save_mac_key", (value "56e19be33eddf58f7c010f35eeac3c2b")
[WARN]: Failed to match key "save_mac_key_source", (value "e4cd3d4ad50f742845a487e5a063ea1f")
[WARN]: Failed to match key "tsec_root_key", (value "e21d3f25bbea7f52f3cdf88b481bde9e")

[9424] Failed to execute script ChoiDujour

I used the method with lockpick to get my keys.txt. But with lockpit there was only a prod.keys file. so i renamed it to keys.txt.
Do you have any solutions for me?

 

[Taorn]

I have tried to follow the guide. but when i try to run the cmd at step 4.3 i get an error.

[...]

I used the method with lockpick to get my keys.txt. But with lockpit there was only a prod.keys file. so i renamed it to keys.txt.
Do you have any solutions for me?

Hey,
the keys.txt and prod.keys are different names for the same file. So you did well with simply renaming it.

As for your problem:
Make a copy of your keys.txt and name it keys_min.txt. Afterwards delete every entry in keys_min.txt that the tool complains about. So, you would delete bis_key_00, bis_key_01 and so on.
After you're done try to pass your keys_min.txt instead of the original keys.txt.

ChoiDujour.exe --keyset=keys_min.txt fw

If you still get warning about your keys_min.txt afterwards, then delete those entries as well. Do this until your file is accepted.

 

[Don328]

Hey,
the keys.txt and prod.keys are different names for the same file. So you did well with simply renaming it.

As for your problem:
Make a copy of your keys.txt and name it keys_min.txt. Afterwards delete every entry in keys_min.txt that the tool complains about. So, you would delete bis_key_00, bis_key_01 and so on.
After you're done try to pass your keys_min.txt instead of the original keys.txt.

ChoiDujour.exe --keyset=keys_min.txt fw

If you still get warning about your keys_min.txt afterwards, then delete those entries as well. Do this until your file is accepted.

now i get this error

Spoiler

>ChoiDujour.exe --keyset=keys.txt fw
Zugriff verweigert

which means "access denied"

 

[Taorn]

now i get this error

Spoiler

>ChoiDujour.exe --keyset=keys.txt fw
Zugriff verweigert

which means "access denied"

That's strange. Is there no output from ChoiDujour itself anymore? In that case, it seems as if you're pc is stopping you from executing it.

Could you post a screenshot of when you're trying to execute the program? A screenshot of the folder you're using would be helpful as well.

 

[Don328]

i think it worked now. rebootet my computer because choidujour wasnt working and now it worked. but i have deleted many keys. will the fw work ?

now im stuck on the next step. when i inject the memloader.bin on my switch it says
"attempting to communicate with usb host ... try 77 (last retVal 3 xfer´d 0 bytes)"

 

[stevemiff1971]

I get choidujour.exe—keyset is not a recognised as an internal or external command error

 

[Don328]

holy fuck it worked. i have a fully working switch on 6.1.0 thankks Taorn.
now im making an nand backup and then i try to update to 9.0.1 with atmosphere

ps. is it normal that i cant start my switch without a payload? i thought i can start the ofw without payload but it doesnt work :/

 

[Taorn]

holy fuck it worked. i have a fully working switch on 6.1.0 thankks Taorn.
now im making an nand backup and then i try to update to 9.0.1 with atmosphere

ps. is it normal that i cant start my switch without a payload? i thought i can start the ofw without payload but it doesnt work :/

Good to hear it worked,congrats!
Did you enable auto rcm? This would explain that. Otherwise your fuse count might be too high to boot 6.1.0 with the Nintendo bootloader. Updating your Switch to 9.0.1 should take care of that problem.

Take good care of your backup. Save it somewhere safe, maybe upload it to Google Drive or another cloud hoster.

 

[Don328]

Good to hear it worked,congrats!
Did you enable auto rcm? This would explain that. Otherwise you‘re fuse count might be too high to boot 6.1.0 with the Nintendo bootloader. Updating your Switch to 9.0.1 should take care of that problem.

Take good care of your backup. Save it somewhere safe, maybe upload it to Google Drive or another cloud hoster.

It was autorcm. Deactivated it and now it is working. Have saved the 6.1.0 Backup and updates to 9.0.1 and then safer the 9.0.1 backup. Now everything works fine. Thank you very much. I am never going to update without a backup again.

But I found out. When I Start atmosphere then it „crashes“ after the two atmosphere logos. So I thought it crashes. But it dont really crashes. It is booting in cfw. But in sx os I just have to go into the album to see the homebrew. In atmosphere I have to click r1 and then go into the album.
So I thing the hole process was not necessary. I could have just updated thru atmosphere. But I thought it wasn’t working. Well my fault but now everything is fine.