Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,134,713
  • Replies Replies 47,989
  • Likes Likes 66
If you want to install Briccmii, you use it in place of fusee_primary.bin. Also you don't install Atmosphere :D

Hi! Thank you for your answer. Can you explain why I wouldn't be able to install Atmosphere?
What should I do, to be able to enjoy the advantages of both?

Thank you!
 
HALP!

I updated my switch from 6.X to 7.X using choinNX . My switch was on real 6.X. I loaded up Choi. Pick the 7.0 folder. It did it's tests and said ready. I installed it. The only thing here was I chose 7.X instead of 7.X exfat. I apparently installed 6.X exfat before and didn't remember.

So it said compete. I shut down the switch. Restarted in RCM. Loaded Hekate payload. Got a atmosphere loading screen. Another loading screen. Then a nintendo logo. Then black.. tried restarting. Nothing.

Tried taking out SD card and booting normal. Nothing. I can still get into RCM and load payload but nothing goes past Nintendo logo. I have a copy of my NAND I believe. How screwed am I?
 
HALP!

I updated my switch from 6.X to 7.X using choinNX . My switch was on real 6.X. I loaded up Choi. Pick the 7.0 folder. It did it's tests and said ready. I installed it. The only thing here was I chose 7.X instead of 7.X exfat. I apparently installed 6.X exfat before and didn't remember.

So it said compete. I shut down the switch. Restarted in RCM. Loaded Hekate payload. Got a atmosphere loading screen. Another loading screen. Then a nintendo logo. Then black.. tried restarting. Nothing.

Tried taking out SD card and booting normal. Nothing. I can still get into RCM and load payload but nothing goes past Nintendo logo. I have a copy of my NAND I believe. How screwed am I?

Just switch from exFAT to FAT32, or redo ChoidujourNX update on FAT32 7.0.x
 
Hi,

Is the activation of SX OS alter the sysNand ?
Because of the guide of activation I can read :

12. Click Boot custom FW on your Switch. When you perform the first time the boot of SX OS a license file (license-request.dat) will be created on your MicroSD cards.
13. After the booting power Off your Switch and put your MicroSD card back to your PC.
14. Visit now Team Xecuters Activation Side, upload your file from the MicroSD (license-request.dat) and manually enter your License Code.
15. Click on Retrieve License and the download of your new license file should start.

So I have to boot on custom FW on sysNand before i can get the .dat licence ?
 
Hi,

Is the activation of SX OS alter the sysNand ?
Because of the guide of activation I can read :

12. Click Boot custom FW on your Switch. When you perform the first time the boot of SX OS a license file (license-request.dat) will be created on your MicroSD cards.
13. After the booting power Off your Switch and put your MicroSD card back to your PC.
14. Visit now Team Xecuters Activation Side, upload your file from the MicroSD (license-request.dat) and manually enter your License Code.
15. Click on Retrieve License and the download of your new license file should start.

So I have to boot on custom FW on sysNand before i can get the .dat licence ?

It say boot into Custom FW, (CFW)
 
Just switch from exFAT to FAT32, or redo ChoidujourNX update on FAT32 7.0.x

When you say redo FAT32, do you mean reformat the card and installins use Choidujour on PC to reinstall 7.0? Because I can boot CFW just go into RCM..

Because I can't even boot into OFW without SD card. Which worries me .
 
When you say redo FAT32, do you mean reformat the card and installins use Choidujour on PC to reinstall 7.0? Because I can boot CFW just go into RCM..

Copy your files off SD, format card to FAT32, copy file back, boot into CFW, and then redo ChoidujourNX to install firmware with exFAT, but then again I wouldn't recommend using exFAT due to corruption issue.

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

Yeah but if I haven't yet set up emuNand it will run CFW on sysNand..
And i want to avoid touching sysNand

You boot into SX OS so that Custom Firmware, (CFW), Stock firmware (OFW) you leave that alone.
 
this morning it updated no issue...was there server down i couldn't find anything online also was able to update os to 7.0.1
 
Hi everyone, i jailbreak using 128GB SD card, and i just got another 128GB SD card to install more games into the new SD card. So i copied all files from the old SD to new SD (including all installed games as i dont know which file is those game located).

So, I on Switch using new SD, and delete all game software from the data management. However, when i click the "album" to install nsp game, it will just showing error as below. I realised that if there is any NSP file in root of SD, there is such error, however I can access the "album" if i create a new folder and put those NSP file in this new folder, and I can't install some game as it showed error.

an error occured attempting to install the nsp
error : 0x234a02
module: FS (2)
description : invalid nca (might mean missing sigpatches or a too low firmware) (4517)

My atmosphere is 0.8.4 with firmware 7.0.1, which i believe its latest version now, and i had no problem to install those game previously, but now showing me with such error when i install the exactly same game. Can anyone tell me what is the error i did? now this problem exist in both old and new SD card...

I also tried to insert the old SD, and all the games were gone, and the SD card showing it was empty. So means i need to install all nsp again?

Thank you very much.
 

Attachments

  • 1111.JPG
    1111.JPG
    82.2 KB · Views: 145
Hi everyone, i jailbreak using 128GB SD card, and i just got another 128GB SD card to install more games into the new SD card. So i copied all files from the old SD to new SD (including all installed games as i dont know which file is those game located).

So, I on Switch using new SD, and delete all game software from the data management. However, when i click the "album" to install nsp game, it will just showing error as below. I realised that if there is any NSP file in root of SD, there is such error, however I can access the "album" if i create a new folder and put those NSP file in this new folder, and I can't install some game as it showed error.

an error occured attempting to install the nsp
error : 0x234a02
module: FS (2)
description : invalid nca (might mean missing sigpatches or a too low firmware) (4517)

My atmosphere is 0.8.4 with firmware 7.0.1, which i believe its latest version now, and i had no problem to install those game previously, but now showing me with such error when i install the exactly same game. Can anyone tell me what is the error i did? now this problem exist in both old and new SD card...

I also tried to insert the old SD, and all the games were gone, and the SD card showing it was empty. So means i need to install all nsp again?

Thank you very much.

Use latest Kosmos and atmosphere build, and add the additional sig patches and the 2.0.0 to 7.0.1 sig patches to the kip patches folder.
 
Do you think I'm okay to go online with sysNand et run xci on emuNand ?

Brand new switch 7.0.1
1 - Factory reset of sysnand and backup raw + boot0/1 withn Henk
2 - Creating emunand on SD with SX OS
3 - Booting into emunand (airplain mode) and run XCI
4 - Disabling AutoRCM
 
ok i will try now. Do you know why is it suddenly happen that I cannot put NSP file on the root of SD now?

Suggestion is to use FAT32, but you gotta split the size of the file if they are larger than 4GB, beside that you might have a faulty card maybe.
 
Hello everyone. I'm currently a sx os user, but I was trying to make Kosmos work but I have a problem. I've followed the set-up guide, prepared my SD and used the sx os to inject the henkate payload, no problem there, the problem is in henkate itself.
When I enter henkate and choose the option cfw it loads then freezes when "loaded pkg1 & key blob" appears.
 
Quick Question:

ChoiDujour doesn't support 6.2.0. Any other way to get that firmware on a console?

I wanted to restore a pre-CFW backup I had. Figured it was safe because I had only done fw upgrades through non-fuse burning methods.

Apparently not so. I now have 8 burnt fuses and no backup of NAND that lives on 6.2.0

I've followed rajkosto's guide (can't link because I'm too nub I guess) as far as I could until I realized that 6.2.0 was not supported by this method.

Unless I'm wrong, until the FW on eMMC matches up to 6.2 I can't boot, regardless of CFW or not yeah? So no sense in using ChoiDujour to get me to 6.1.0
 
Quick Question:

ChoiDujour doesn't support 6.2.0. Any other way to get that firmware on a console?

I wanted to restore a pre-CFW backup I had. Figured it was safe because I had only done fw upgrades through non-fuse burning methods.

Apparently not so. I now have 8 burnt fuses and no backup of NAND that lives on 6.2.0

I've followed rajkosto's guide (can't link because I'm too nub I guess) as far as I could until I realized that 6.2.0 was not supported by this method.

Unless I'm wrong, until the FW on eMMC matches up to 6.2 I can't boot, regardless of CFW or not yeah? So no sense in using ChoiDujour to get me to 6.1.0

Not that ChoidujourNX doesn't support 6.2.0, since you have 8 burn fuse lowest firmware you can boot without a bootloader is 6.2.0.
 
Not that ChoidujourNX doesn't support 6.2.0, since you have 8 burn fuse lowest firmware you can boot without a bootloader is 6.2.0.

ChoidujourNX does support 6.2.0, ChoiDujour for PC does not.

Currently boot just gives me an ugly blue screen. Is there no method by which I can get 6.2.0 on my NAND without having a backup of that version?
 

Site & Scene News

Popular threads in this forum