Hacking Can I please get help. I’m actually very depressed now

[saggan]

Prodinfo is part of your NAND partition which stores all the important stuff.

how to do that

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

1. Download:
-Latest Atmosphere 0.8.1
-Latest Fusee Primary

2. Insert ATMOSPHERE folder in your fat32 sdcard

3. Use TegraRCM to inject the latest Fusee Primary

4. Let us know if it still doesn't work

i'll give it a try

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

i tried the non nx-version
i get failed to match key

 

[PrEtZaL]

Firmware 6.2.0 isn't compatible with hekate yet only fusee primary payload will work and you need to use Atmosphere 0.8.1.....launching cfw or ofw hekate will result in a black screen.

Either that or use Nintendo boot loader to go OFW since you've already burnt 8 fuses......but CFW in 6.2.0 requires the fusee payload as mentioned above.

If you want to use hekate you'll need to add a custom ini to the payloads folder which just chainloads the fusee primary.

However if you're now on 5.1 via restoring your nand you'll need to rebuild boot0 and boot1 or restore them from 5.1 since the boot files will be a different version to the firmware.

 

[saggan]

Firmware 6.2.0 isn't compatible with hekate yet only fusee primary payload will work and you need to use Atmosphere 0.8.1.....launching cfw or ofw hekate will result in a black screen.

Either that or use Nintendo boot loader to go OFW since you've already burnt 8 fuses......but CFW in 6.2.0 requires the fusee payload as mentioned above.

If you want to use hekate you'll need to add a custom ini to the payloads folder which just chainloads the fusee primary.

i used atmosphere 0.8.1 through fusee primary payload
got the atmosphere logo then the nintendo logo
and freeze with black screen

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

1. Download:
-Latest Atmosphere 0.8.1
-Latest Fusee Primary

2. Insert ATMOSPHERE folder in your fat32 sdcard

3. Use TegraRCM to inject the latest Fusee Primary

4. Let us know if it still doesn't work

didnt work
freezes after nintendo logo

 

[8BitWonder]

i tried the non nx-version
i get failed to match key

Your SD should have the following items/folders on the root when pushing fusee-primary, does this match your sd card?

atmosphere\
  L kip_patches\
      L default_nogc\
          L ...
  L titles\
     L 0100000000000032\
          L ...
     L 0100000000000034\
          L ...
     L 0100000000000036\
          L ...
  L loader.ini
BCT.ini
fusee-secondary.bin

 

[PrEtZaL]

It's sounds as though you've got 6.2 boot files with a 5.1 firmware then from what I've understood in your initial post

 

[saggan]

Your SD should have the following items/folders on the root when pushing fusee-primary, does this match your sd card?

atmosphere\
  L kip_patches\
  L titles\
     L 0100000000000032\
     L 0100000000000034\
     L 0100000000000036\
  L loader.ini
BCT.ini
fusee-secondary.bin

no i got the atmosphere folder and primary fusee
secondary fusee
only on the root of my card

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

It's sounds as though you've got 6.2 boot files with a 5.1 firmware then from what I've understood in your initial post

yes

 

[8BitWonder]

no i got the atmosphere folder and primary fusee
secondary fusee
only on the root of my card

Extract the zip on this page to the root of your SD card, than try pushing fusee-primary again.
It sounds like you might be missing BCT.ini (which is included in that zip).

 

[PrEtZaL]

Extract the zip on this page to the root of your SD card, than try pushing fusee-primary again.
It sounds like you might be missing BCT.ini (which is included in that zip).

If this doesn't work look at

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Concentrate on the boot0 and boot1 section and section 9 onwards in respect of rebuilding the boot files which will be AutoRCM by default

 

[saggan]

Extract the zip on this page to the root of your SD card, than try pushing fusee-primary again.
It sounds like you might be missing BCT.ini (which is included in that zip).

same problem
after the atmosphere logo nothing but black

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

If this doesn't work look at

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Concentrate on the boot0 and boot1 section and section 9 onwards in respect of rebuilding the boot files which will be AutoRCM by default

tried it
actually trying it from yesterday and got stuck in step 7

 

[PrEtZaL]

Make sure you put "" around both paths to the keys.txt and the fw location.

Choidujour -- keyset="path\keys.txt" "pathtofw"

You want to use fw 5.1

Once it works you need to only use the boot0, boot1 and files in the microsd folder

 

[saggan]

Make sure you put "" around both paths to the keys.txt and the fw location.

You want to use fw 5.1

Once it works you need to only use the boot0, boot1 and files in the microsd folder

C:\Users\AAA\Desktop\ChoiDujour110>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 "master_kek_04", (value "xxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "master_kek_05", (value "xxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "master_kek_02", (value "xxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "master_kek_03", (value "xxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "master_kek_00", (value "xxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "master_kek_01", (value "xxxxxxxxxxxxxxxx")

[3560] Failed to execute script ChoiDujour

C:\Users\AAA\Desktop\ChoiDujour110>

this is what happens

 

[PrEtZaL]

You don't have any paths in that command line

C:\Users\AAA\Desktop\ChoiDujour110>ChoiDujour.exe --keyset="C:\Users\AAA\Desktop\ChoiDujour110\keys.txt" "C:\Users\AAA\Desktop\ChoiDujour110\fw"

If your keys.txt and fw folder are in the choidujour folder

 

[saggan]

You don't have any paths in that command line

yes
the keys.txt and the fw file both in the ChoiDujour file

 

[PrEtZaL]

yes
the keys.txt and the fw file both in the ChoiDujour file

Try that command line then

 

[comput3rus3r]

Please someone give me any tips

What to do with the black screen

I was on sx os 2.3 beta pressed update by mistake and updated the fw from 5.1 to 6.2

So I used ns atmosphere to run homebrew and downgraded to 5.1 which was the mistake so I went to the sx os options and also by stupid mistake I pressed on load EmuNAND which is nothing there and all I get now is black screen and I formatted my SD card several times trying to load different payloads which I can but after the payload logo I get black screen and the console freezes

I checked for the Burnt fuses and they are 8 now


Is there any way to even load the ofw or can some donor give me a backup that could work with me

or a factory reset

Or should I just throw it away and buy a new one which will cost me a lot again

out of curiosity why weren't you using emunand?

 

[saggan]

out of curiosity why weren't you using emunand?

i have no emunand backup

 

[comput3rus3r]

i have no emunand backup

yes but why not?

 

[saggan]

out of curiosity why weren't you using emunand?

i didn't know i should backup my emunand

 

[PrEtZaL]

out of curiosity why weren't you using emunand?

The emunand flag on the boot file will have been overwritten when he updated to 6.2

 

[comput3rus3r]

i didn't know i should backup my emunand

no i mean if you had been using emunand to begin with and you mistakenly updated, your sysnand would still be fine.

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

The emunand flag on the boot file will have been overwritten when he updated to 6.2

if you update in emunand your sysnand remains untouched afaik.