Hacking SWITCH NOOB PARADISE - Ask questions here

[binkinator]

I experience the same problem as you when installing xenoblade. 14.1.2 atmosphere 1.3.2.
installed the game with goldleaf, awoo.. everything installs but the game never starts. From where did you replaced Atmosphere, Hekate and Sigpatches?

You can use PC method here:

https://rentry.org/UpdateCFW

 

[clianvXAi]

You can use PC method here:

https://rentry.org/UpdateCFW

Thanks, tried this, but no luck. Still get this message “the software was closed because an error occurred“.

 

[binkinator]

Thanks, tried this, but no luck. Still get this message “the software was closed because an error occurred“.

Try these:

Sigpatches (GBATemp) — alternative Sigpatches for when others don’t seem to work.

 

[clianvXAi]

I guess I should wait for some Sigpatches updates. None of them seem to work. It’s strange, cause every other game works with no problem.

 

[binkinator]

I guess I should wait for some Sigpatches updates. None of them seem to work. It’s strange, cause every other game works with no problem.

Try maintenance mode (just steps 1 and 2 and then reboot…don’t change anything…just reboo)

https://en-americas-support.nintend...to-update-nintendo-switch-in-maintenance-mode

 

[Draxzelex]

Hi Guys,

I copied my 128gb fat32 SD card contents on to a 512gb card which I formatted first to exfat.

I copied all the contents to replace the older atmosphere with the latest 1.3.2 version.

I updated the firmware via Daybreak from 13.1 to 14.1 (selecting exfat + fat32 option)

The bootloader has the hetake_ipl.ini

Using Tegra RCM to boot with the latest hetake.bin file.

When I try to boot into CFW (emuMMC) I get the error: unknown pkg1 version, HOS version not supported or emummc corrupted.

I have the latest sigpatches too.

What steps have I missed? Please help

Format the SD card to FAT32. exFAT is notorious for corrupting the SD card.

 

[demoneyes10000]

Format the SD card to FAT32. exFAT is notorious for corrupting the SD card.

Thanks for your response. That should fix it? Otherwise it's a lengthy process

 

[Draxzelex]

Thanks for your response. That should fix it? Otherwise it's a lengthy process

Wait a minute. You said you copied all your contents from one SD card to another. Did you also copy the emuMMC from the first SD card to the second one? If you are trying to boot emuMMC, that would explain the issue if you didn't move the emuMMC over or didn't make a new on the 512 GB SD card.

 

[demoneyes10000]

I did, I copied the emuMMC folder over to the 512gb card and can see the emuMMC folder with its contents RAW1 folder and emummc.ini file (size 77gb) Do I need to create another emu on this card via atmos emu menu?

 

[Draxzelex]

I did, I copied the emuMMC folder over to the 512gb card and can see the emuMMC folder with its contents RAW1 folder and emummc.ini file (size 77gb) Do I need to create another emu on this card via atmos emu menu?

Let me answer your question with another question: do you use partition or file based emuMMC?

 

[demoneyes10000]

Let me answer your question with another question: do you use partition or file based emuMMC?

type: SD Raw Partition

 

[clianvXAi]

Try maintenance mode (just steps 1 and 2 and then reboot…don’t change anything…just reboo)

https://en-americas-support.nintend...to-update-nintendo-switch-in-maintenance-mode

Thx for your time, nothing works. Anyway, i’m done with this game, have a good day.

 

[binkinator]

Thx for your time, nothing works. Anyway, i’m done with this game, have a good day.

Huh. Nothing’s working. That sucks.

Only thing I can think of at this point is deleting the game using Settings -> Data Management and then reinstalling it from another source.

e: might have to delete game saves as well.

 

[Draxzelex]

type: SD Raw Partition

Then that fully explains your problem. Copying the emuMMC folder only copied the files pertaining to your emuMMC. Your emuMMC is a partition which isn't a file that you can simply copy and paste; its something that has be to backed up via Hekate or dumped as an image with an SD partitioning tool such as Minitool Partition Wizard, then after using either method, flash the partition onto the new SD card.

 

[demoneyes10000]

Then that fully explains your problem. Copying the emuMMC folder only copied the files pertaining to your emuMMC. Your emuMMC is a partition which isn't a file that you can simply copy and paste; its something that has be to backed up via Hekate or dumped as an image with an SD partitioning tool such as Minitool Partition Wizard, then after using either method, flash the partition onto the new SD card.

Thanks, I'll try to work out getting it over to the new card from the old.

 

[PREO]

So heat is a weird phenomenon. It spreads around and stores up and dissipates. It’s not an all or nothing thing. Just clicking around and lower demand games are probably able to get by with ambient air pulling just enough heat away to not crash the machine. Heck, your fan may be able to spin a little bit, just not full speed. Once you overheat there is a certain amount of heat that’s going to have been generated but hasn’t spread through the cooling system yet. it can be just enough to take out the game first and even though you’re letting it cool there’s still collected heat that needs to be dealt with that continues to then lock up the entire machine. You should take your back shell off so you can more directly observe the fan.

Ok friend,
I've tried a few experiments and I can tell you this:

- it's not a ìn SD issue, even with no SD in, the original cartridge of BOTW (a working one, run smooth on a second Nintendo Switch) crashes after some time
- it's not an overheating problem, I played the BOTW cartridge for about 15 min, then put the switch in sleep mode for a whole day to let it cool down, and then - after 5 or 6 min - the game closed because an error occured (the switch was cold as hell). Same error of the NSP on the emunand and same behaviour of the Switch afterward.

 

[binkinator]

Ok friend,
I've tried a few experiments and I can tell you this:

- it's not a ìn SD issue, even with no SD in, the original cartridge of BOTW (a working one, run smooth on a second Nintendo Switch) crashes after some time
- it's not an overheating problem, I played the BOTW cartridge for about 15 min, then put the switch in sleep mode for a whole day to let it cool down, and then - after 5 or 6 min - the game closed because an error occured (the switch was cold as hell). Same error of the NSP on the emunand and same behaviour of the Switch afterward.

E: great troubleshooting BTW. Really cuts down the noise of potential issues.
I think we’re at the point of needing to take it in to a shop and have someone look at it.
I’ve exhausted my bank of ideas short of a real hardware problem.
Anyone else want to take a shot here?

 

[Draxzelex]

I read the FAQ and am aware several discussions exist, there is a ton of info but I’m not sure what’s current, so sorry ahead of time.

I have a launch switch running 14.1.2, I am pretty familiar with cfw for most systems. I’ve never cfw’ed my switch, all original. All I’m trying to accomplish is offline cheats or hack game saves (ala save wizard ps4). Is there a dongle or something that accomplishes this? Or do I have to go the CFW route? I have some games through eshop and would like to play stock online rarely. Is it the console or the account that gets banned? Is there still a way to fully revert to stock if the CFW route is necessary? Any help is greatly appreciated. You don’t have to answer directly just point me in the right direction. Thank you so much for your patience!

All dongles and modchips all just used to enable CFW so either way, you will need CFW in the end. All bans primarily affect the console. Account bans are limited to other activities such as credit card fraud. And the only way to fully revert to stock is by restoring an eMMC backup made before ever running CFW and/or homebrew. I highly recommend following this guide to setup CFW

 

[Prilann]

I followed the soldering guide by sthetix. All soldering points where checked by a multimeter. Only the B point (RST) got slightly higher value with 3.1V.
No grounds so far. Chip updated to newest firmware 0.7.0. I resoldered most parts except CPU and DAT0. Any ideas what I could check?

First it starts by red blinking and then it turns into a red/yellow/green loop.

 

[demoneyes10000]

Then that fully explains your problem. Copying the emuMMC folder only copied the files pertaining to your emuMMC. Your emuMMC is a partition which isn't a file that you can simply copy and paste; its something that has be to backed up via Hekate or dumped as an image with an SD partitioning tool such as Minitool Partition Wizard, then after using either method, flash the partition onto the new SD card.

So I followed this guide https://nh-server.github.io/switch-guide/extras/transfer_sd/ I partitioned the new SD card, copied contents of the old SD card over including the emu backup Boot10 Boot1 and RAWGPP files. I then restored the emu and got the message partition not found. Tried booting into CFW Emummc and get the same PKG1 HOS error. What am I missing?