Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,024,178
  • Replies Replies 47,921
  • Likes Likes 66
Hello I have a question: so when restoring a save on Syscfw offline for a physical cart and need to launch hbl on syscfw offline

Do you do Hold down R while opening album or holding the R button while launching any game (including demos/cartridges) while on syscfw offline?
 
Hello I have a question: so when restoring a save on Syscfw offline for a physical cart and need to launch hbl on syscfw offline

Do you do Hold down R while opening album or holding the R button while launching any game (including demos/cartridges) while on syscfw offline?
nah, you dont need title override for most hb apps. just open album
 
Last edited by Windsall,
I could try, though I'd really like it if the other controllers would work, since the joycons are small and I like to leave them on the switch most of the time.

My line of reasoning is that we have a step by step for getting two players going. Once that’s working you can go back and swap in a new Pro or what have you with the knowledge that everything was working just prior. Basically following the approach of changing one variable at a time from a known good state.
 
  • Like
Reactions: Windsall
Hello all.

Yesterday I updated my hacked switch to 14.1 with Switch AiO Updater. Everything went smooth except in the end, I accidentally selected Fat32. My SD is in exFAT and now I can not boot.

I don't want to risk loosing my data with formatting my SD to FAT32, so I used a new card, formatted as FAT32, to enter again and Update to 14.1 and selecting FAT32+exFAT this time. Everything went smooth, but when I put back my original SD, I have the same problem. "Your console has non-exFAT firmware installed but your SD card is formatted as exFAT' !!!

Can you help ?
 
Hello all.

Yesterday I updated my hacked switch to 14.1 with Switch AiO Updater. Everything went smooth except in the end, I accidentally selected Fat32. My SD is in exFAT and now I can not boot.

I don't want to risk loosing my data with formatting my SD to FAT32, so I used a new card, formatted as FAT32, to enter again and Update to 14.1 and selecting FAT32+exFAT this time. Everything went smooth, but when I put back my original SD, I have the same problem. "Your console has non-exFAT firmware installed but your SD card is formatted as exFAT' !!!

Can you help ?
 
My line of reasoning is that we have a step by step for getting two players going. Once that’s working you can go back and swap in a new Pro or what have you with the knowledge that everything was working just prior. Basically following the approach of changing one variable at a time from a known good state.

Thanks, makes sense, I'll see about trying sometime and see what I can get from it.
 
  • Like
Reactions: binkinator
Hello all.

Yesterday I updated my hacked switch to 14.1 with Switch AiO Updater. Everything went smooth except in the end, I accidentally selected Fat32. My SD is in exFAT and now I can not boot.

I don't want to risk loosing my data with formatting my SD to FAT32, so I used a new card, formatted as FAT32, to enter again and Update to 14.1 and selecting FAT32+exFAT this time. Everything went smooth, but when I put back my original SD, I have the same problem. "Your console has non-exFAT firmware installed but your SD card is formatted as exFAT' !!!

Can you help ?

if the cards are the same size (or the new one is bigger) you can do a bit-for-bit copy from old to new sd cards using Minitool Partition Wizard. Then, using the same tool, go back and format the exfat partition on the new copy as FAT32. Now go back and copy the data from your old exfat partition to yiur new FAT32 partition and when done, boot up you new sd card.
 
Last edited by binkinator,

I'm afraid this is out of the question, because my SD is 512Gb and I'm too scared to lose files. So, I would prefer the other way, that is to enable exFAT on my Switch. Any ideas what am I doing wrong ?
 
I'm afraid this is out of the question, because my SD is 512Gb and I'm too scared to lose files. So, I would prefer the other way, that is to enable exFAT on my Switch. Any ideas what am I doing wrong ?

Not sure I follow. This in no way endangers any of your files regardless of your sd card size. I use 400Gb FAT32 cards for both of my switches. Highly recommended.

I personally don’t want to aid in the use of exfat due to the inferior exfat drivers Ninty went with on the Switch.

I will note that you can look at my suggestion above and reverse the order a bit and do your own thing with exfat…I just don’t want to be the guy that loaded your revolver. :)
 
Not sure I follow. This in no way endangers any of your files regardless of your sd card size. I use 400Gb FAT32 cards for both of my switches. Highly recommended.

I personally don’t want to aid in the use of exfat due to the inferior exfat drivers Ninty went with on the Switch.

I will note that you can look at my suggestion above and reverse the order a bit and do your own thing with exfat…I just don’t want to be the guy that loaded your revolver. Is there a reason why what I did, did not work ? Isn't my though OK ? I updated my Switch to 14.1.0 WITH exFAT using a new SD and then returned to my original SD ... Why is that not working ???
 
Is there a reason why what I did, did not work ?
by not including the (extra and non-standard) exfat drivers you made the partition unreadable. You need to get to a state where the drivers are included. You could do this using Daybreak once yiu get control of your partition again.
Isn't my though OK ?
Which one? FAT32 is more stable and all modern installers know how to handle installing 4Gb+ games onto it. Exfat is a homegrown Ninty implementation that is well documented to cause corruption. Corruption on a FAT32 sd card will corrupt one file. Corruption on an exfat partition will corrupt the entire partition. exfat is more risky.
I updated my Switch to 14.1.0 WITH exFAT using a new SD and then returned to my original SD ... Why is that not working ???
The drivers are inside the FW you deployed to your emunand. When it gets past the bootloader and tries to read the partition using the missing drivers it will be unable to read the card.
 
by not including the (extra and non-standard) exfat drivers you made the partition unreadable. You need to get to a state where the drivers are included. You could do this using Daybreak once yiu get control of your partition again.

Which one? FAT32 is more stable and all modern installers know how to handle installing 4Gb+ games onto it. Exfat is a homegrown Ninty implementation that is well documented to cause corruption. Corruption on a FAT32 sd card will corrupt one file. Corruption on an exfat partition will corrupt the entire partition. exfat is more risky.

The drivers are inside the FW you deployed to your emunand. When it gets past the bootloader and tries to read the partition using the missing drivers it will be unable to read the card.
By "what I did" I mean "I used a new card, formatted as FAT32, to enter again and Update to 14.1 and selecting FAT32+exFAT this time. Everything went smooth, but when I put back my original SD, I have the same problem. "Your console has non-exFAT firmware installed but your SD card is formatted as exFAT"
 
By "what I did" I mean "I used a new card, formatted as FAT32, to enter again and Update to 14.1 and selecting FAT32+exFAT this time. Everything went smooth, but when I put back my original SD, I have the same problem. "Your console has non-exFAT firmware installed but your SD card is formatted as exFAT"

Let me ask this a different way…

When you say you “update to 14.1”…are you upgrading the Sysnand or Emunand?

  • If you are upgrading the Sysnand that’s great. Are you then booting to CFW/Sysnand on your old sd card or are you booting to the Emunand contained on that card which is still FAT32 only.

  • If you are upgrading Emunand that’s good, however it’s only doing so on the new sd card you have just inserted at that moment. When you swap out the card you swap out the FW again and thus go back to the original sd card with the FAT32 only FW.
 
Let me ask this a different way…

When you say you “update to 14.1”…are you upgrading the Sysnand or Emunand?

  • If you are upgrading the Sysnand that’s great. Are you then booting to CFW/Sysnand on your old sd card or are you booting to the Emunand contained on that card which is still FAT32 only.

  • If you are upgrading Emunand that’s good, however it’s only doing so on the new sd card you have just inserted at that moment. When you swap out the card you swap out the FW again and thus go back to the original sd card with the FAT32 only FW.

I put a new SD, that I have atmosphere, hekate and a firmware folder. I inject fusee and go to daybreak to install the firmware.
Then i put my original SD, I inject fusee again and I'm where I started ...
 
I put a new SD, that I have atmosphere, hekate and a firmware folder. I inject fusee and go to daybreak to install the firmware.
Then i put my original SD, I inject fusee again and I'm where I started ...
Right…but which *nand are you installing the firmware on? Sysnand or Emunand?
 
Last edited by binkinator,
How can I tell ? I didn't have to choose ... did I ?
Most probably it is EmuNAND since it doesn't work when I change the SDs ...
What do you see here:
Settings —> System —> System Update
1649701065583.jpeg
 

Site & Scene News

Popular threads in this forum