Hacking Question ChoiDujour Doesn't Work, Can't Downgrade

[Marlap2000]

I made a thread yesterday about this and how I keep getting the "Section 0 is corrupted" error in Choi. Can someone run their Choi and keys for a 6.1 or 6.0.1 firmware and DM me a link to the file? As far as I'm aware, the Choi files it makes aren't console specific if you use online keys and a firmware downloaded from the internet. I can't get Choi to work myself for some reason so if somebody has a file that they made through Choi and can share it that would be great. Thanks.

 

[Hayato213]

People can't link you system update file here on the forum via post or DM.

 

[Marlap2000]

People can't link you system update file here on the forum via post or DM.

Where can I find that file then?

 

[Hayato213]

Where can I find that file then?

ChoidujourNX, is more of an update, you can't really downgrade and boot into OFW if you burned your fuse. You can look for the firmware file from normally where you get your warez, don't asks for link here.

 

[Marlap2000]

ChoidujourNX, is more of an update, you can't really downgrade and boot into OFW if you burned your fuse. You can look for the firmware file from normally where you get your warez, don't asks for link here.

I'm using ChoiDujour, not NX, to downgrade from 7.0.0 to 6.1.0. I can't get the Choi to give me a file because it doesn't want to run.

 

[Hayato213]

I'm using ChoiDujour, not NX, to downgrade from 7.0.0 to 6.1.0. I can't get the Choi to give me a file because it doesn't want to run.

You can't downgrade and boot into OFW if you burned your fuse, downgrade is done by restoring your NAND backup if your fuse is intact.

 

[PrEtZaL]

You can't downgrade and boot into OFW if you burned your fuse, downgrade is done by restoring your NAND backup if your fuse is intact.

Wrong, you can boot into any fw OFW or CFW regardeless of fuses burnt if you use a payload to avoid the check.

 

[Hayato213]

Wrong, you can boot into any fw OFW or CFW regardeless of fuses burnt if you use a payload to avoid the check.

Well Im talking about without any payload

 

[PrEtZaL]

Well Im talking about without any payload

Not very clear in your response. You said you can't downgrade if you've burnt fuses......any how sounds like the OP has never used choidujour, suggest you wait for 7 support

 

[Philliyxx]

I'm using ChoiDujour, not NX, to downgrade from 7.0.0 to 6.1.0. I can't get the Choi to give me a file because it doesn't want to run.

I'll get the files when I get home later. We will figure out how to get them to you off of gbatemp

 

[Marlap2000]

You can't downgrade and boot into OFW if you burned your fuse, downgrade is done by restoring your NAND backup if your fuse is intact.

I have Hekate on this switch and AutoRCM works. I updated accidentally from 6.2 to 7.0 and now atmosphere won't boot. There's a pretty long guide on guide dot sdsetup dot com on how to downgrade if you're in my situation. I've done a NAND backup and followed the guide all the way to the point where I have to use Choi on my PC and give it a firmware and keys to give me a usable firmware package I can use to downgrade. Downgrading this way disregards fuses I'm pretty sure.

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

Not very clear in your response. You said you can't downgrade if you've burnt fuses......any how sounds like the OP has never used choidujour, suggest you wait for 7 support

I followed the guide that I use step by step and even with the correct keys and firmware, Choi just doesn't want to run for me. It keeps giving me a

"File "ChoiDujour.py", line 517, in <module>
File "ChoiDujour.py", line 225, in call_hactool
Exception: Error: section 0 is corrupted!File "ChoiDujour.py", line 517, in <module>
File "ChoiDujour.py", line 225, in call_hactool
Exception: Error: section 0 is corrupted!"

error and I have no idea how to fix it.

 

[Hayato213]

I have Hekate on this switch and AutoRCM works. I updated accidentally from 6.2 to 7.0 and now atmosphere won't boot. There's a pretty long guide on guide dot sdsetup dot com on how to downgrade if you're in my situation. I've done a NAND backup and followed the guide all the way to the point where I have to use Choi on my PC and give it a firmware and keys to give me a usable firmware package I can use to downgrade. Downgrading this way disregards fuses I'm pretty sure.

There is no public release of Atmosphere at the moment, you can either find the 6.2.0 files and use choidujour with it, but you gonna have to use AutoRCM with it if you don't want to run into ofw not booting, or you can just wait for 7.0.0 support.

 

[stephrk398]

There is no public release of Atmosphere at the moment, you can either find the 6.2.0 files and use choidujour with it, but you gonna have to use AutoRCM with it if you don't want to run into ofw not booting, or you can just wait for 7.0.0 support.

"You cannot downgrade directly to 6.2.0 as the ChoiDujour PC application does not support 6.2.0. You must downgrade to any other firmware version first and then upgrade back to 6.2.0 with ChoiDujourNX if you specifically want 6.2.0"

Source: https://guide.sdsetup.com/#/Manualchoidowngrade

 

[Kafluke]

I have Hekate on this switch and AutoRCM works. I updated accidentally from 6.2 to 7.0 and now atmosphere won't boot. There's a pretty long guide on guide dot sdsetup dot com on how to downgrade if you're in my situation. I've done a NAND backup and followed the guide all the way to the point where I have to use Choi on my PC and give it a firmware and keys to give me a usable firmware package I can use to downgrade. Downgrading this way disregards fuses I'm pretty sure.

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


I followed the guide that I use step by step and even with the correct keys and firmware, Choi just doesn't want to run for me. It keeps giving me a

"File "ChoiDujour.py", line 517, in <module>
File "ChoiDujour.py", line 225, in call_hactool
Exception: Error: section 0 is corrupted!File "ChoiDujour.py", line 517, in <module>
File "ChoiDujour.py", line 225, in call_hactool
Exception: Error: section 0 is corrupted!"

error and I have no idea how to fix it.

That guide will help you to downgrade but you still wont be able to boot OFW without a custom boot loader on every boot. Once your fuses are burnt they're burnt forever. If you have a sysnand on 7.0 and you didnt get there by using choidejourNX with autoRCM you will never be able to boot OFW (coldboot OFW) again without running RCM and custom payload on every boot. If you're okay with that then go ahead and downgrade

 

[Zumoly]

OP I suggest you make a NAND backup of your 7 FW (just in case).
Also if you're not familiar with Choixdujour on PC, just wait a few more days till CFW for 7 drops.

 

[Release]

I'll get the files when I get home later. We will figure out how to get them to you off of gbatemp

You think you could help me? I'm getting the same error

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: Error: section 0 is corrupted!

I don't really know if its my keys or what.

 

[Philliyxx]

You think you could help me? I'm getting the same error

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: Error: section 0 is corrupted!

I don't really know if its my keys or what.

Probably keys...I have the 6.1 fw I did for marlap and he said it worked. Where are all your files and what cmds are you running to find your keys?

 

[Release]

Probably keys...I have the 6.1 fw I did for marlap and he said it worked. Where are all your files and what cmds are you running to find your keys?

I had got the file from marlap that ChoiDujour makes, and gotten all the way to launch FS600-exfat_nocmac_nogc.kip1 but never boots.

I've restored my backup and tried again same results.

 

[Philliyxx]

What cfw are you trying to boot. What does your SD card file structure look like. Fat 32 or exfat? What happens when you try and boot

 

[Release]

Im trying to boot the FS600-exfat_nocmac_nogc.kip1 like the tutorial says. Says to make sure system successfully boots, but it sits at a black screen. My sd card is exFAT, and has only Atmosphere on it.