Hacking SWITCH NOOB PARADISE - Ask questions here

[binkinator]

Just upgraded to a 1tb sd card followed the guide online booted into emunand and I get the error "unable to access mi ro sd card"

Any ideas how to fix this all the files are there??

Which guide did you use? Are you using a hidden partition or files for your emunand?

 

[Draxzelex]

It says ""HOS panic occured!" Colour: ####, Code: 06 Press any key..."
I have tried to reinstall my contents atmosphere and everything and I cant find any troubleshooting pages about this issue anywhere even though being one of them first results when searching "HOS panic" on google. could anyone help me with this issue?

We need some more details. Is your console unpatched or patched? Have you hacked it before? What firmware is it on? What version of Atmosphere were you trying to setup?

 

[pupuz]

Thanks - found this one, will give it a try, not sure if it's legit
https://www.sthetix.info/fixing-the-sysnand-the-emunand-with-the-emmchaccgen/

If you're interested - I tried it, after some messing with my emunand, it said "done" but then I've received the same black screen after atmosphere logo, back to first base(( Now I'm starting from scratch, new partition, new emummc, hopefully saves are backed up.

 

[RRuler]

I need to update my Switch, to play newer games.

I am currently on 12.0.1 and Atmosphere 0.19.1.
I have the 1. Generation Switch with the fusee exploit.

I was just wondering what approach would be best here.
I don't really want to update to 15.0, as it does not seem worth it right now.
Also, I don't really feel comfortable to update through the OFW, because I fear my console would be banned (Would not be the end of the world, but why risk it).

I have no emunand. So everything is on one partition.

I thought about just updating through daybreak, I have obtained a 14.1.2 Firmware through the Internet for this.
So I would update Atmosphere to 1.3.2 and update Hekate and stuff according to the guide out there and then update to 14.1.2 through Daybreak.

Will this be fine? I read about the Switch bootloader burning fuses (Though, that should only prevent me from downgrading to anything below 14.1.2, right? And only IF the switch boots through its own bootloader. Right now I got auto-RCM).

Just want to make sure I do nothing wrong here.

Also, I am currently not at home and don't have a jig with me.
I've read that updating through the official firmware will remove Auto-RCM.
From what I read updating through daybreak however will not do this, is that correct?

 

[Draxzelex]

I need to update my Switch, to play newer games.

I am currently on 12.0.1 and Atmosphere 0.19.1.
I have the 1. Generation Switch with the fusee exploit.

I was just wondering what approach would be best here.
I don't really want to update to 15.0, as it does not seem worth it right now.
Also, I don't really feel comfortable to update through the OFW, because I fear my console would be banned (Would not be the end of the world, but why risk it).

I have no emunand. So everything is on one partition.

I thought about just updating through daybreak, I have obtained a 14.1.2 Firmware through the Internet for this.
So I would update Atmosphere to 1.3.2 and update Hekate and stuff according to the guide out there and then update to 14.1.2 through Daybreak.

Will this be fine? I read about the Switch bootloader burning fuses (Though, that should only prevent me from downgrading to anything below 14.1.2, right? And only IF the switch boots through its own bootloader. Right now I got auto-RCM).

Just want to make sure I do nothing wrong here.

Honestly, you have everything down pat from the process to the reasoning. Nothing let to do but just do it. Feel free to ask any more questions or concerns if you have.

 

[RRuler]

Honestly, you have everything down pat from the process to the reasoning. Nothing let to do but just do it. Feel free to ask any more questions or concerns if you have.

Thanks for the quick answer!
So updating through daybreak, even though everything (OFW & CFW) is on one partition will be no problem, thats good.

What about Auto-RCM? Will the update through daybreak disable Auto-RCM?
Cause I got no jig with me right now.

 

[Draxzelex]

Thanks for the quick answer!
So updating through daybreak, even though everything (OFW & CFW) is on one partition will be no problem, thats good.

What about Auto-RCM? Will the update through daybreak disable Auto-RCM?
Cause I got no jig with me right now.

System updates normally remove AutoRCM however when updating through a homebrew app, there is an option on whether you want to keep AutoRCM enabled or not. If I remember correctly, its set to keep AutoRCM enabled by default with Daybreak.

 

[SomethingRando]

We need some more details. Is your console unpatched or patched? Have you hacked it before? What firmware is it on? What version of Atmosphere were you trying to setup?

I was using version 1.3.2. I used the all-in-one updater to install the files for the 15.0.0 version of the official switch firmware. I then went straight to daybreak and chose the firmware folder and installed that. My switch booted in to atmosphere but when I tried to boot the "HOS panic" error appeared and I looked at the tutorial on how to do this and apparently there was many steps I missed to update the switchs firmware version.

 

[pupuz]

Well, my story looks like far from over. About a week ago Home button stopped working, I've tried to reboot and got the black screen. With a lot of help here we've figured out that emuNAND was to to blame, corrupt or whatever. I've started over, formatted microSD to FAT32 and installed new emuMMC partition on it. Updated fw to 14.1.0, started copying via DBI, and after 3 games put on microSD I got write errors from DBI, then after restart - yellow panic 010041544D530000 error message from Atmosphere. Tried to eject the SD and figure out if I can check it for errors or format it - turned out Switch has made the card read-only, I can't format it on Wndows or a Mac, only errors. Does it mean the card is dead and if anything can be done at this point? It's Samsung EVO, bought via Samsung website, fake proof and considered reliable. Second week in despair.

 

[Draxzelex]

I was using version 1.3.2. I used the all-in-one updater to install the files for the 15.0.0 version of the official switch firmware. I then went straight to daybreak and chose the firmware folder and installed that. My switch booted in to atmosphere but when I tried to boot the "HOS panic" error appeared and I looked at the tutorial on how to do this and apparently there was many steps I missed to update the switchs firmware version.

Well, you should not have updated to firmware 15.0 in the first place as its quite unstable which is probably contributing to half of the issue. The other half comes from using the AIO Updater which is also notorious for giving users issues. I recommend deleting your /atmosphere and /sept folders then downloading the new ones from the official Atmosphere GitHub page. If you also have Hekate setup, try running the archive bit fix which can be found under Tools.

 

[SomethingRando]

Well, you should not have updated to firmware 15.0 in the first place as its quite unstable which is probably contributing to half of the issue. The other half comes from using the AIO Updater which is also notorious for giving users issues. I recommend deleting your /atmosphere and /sept folders then downloading the new ones from the official Atmosphere GitHub page. If you also have Hekate setup, try running the archive bit fix which can be found under Tools.

Apparently updating to Atmospher 1.4.0 worked for me? idk what I did but nows its fixed. Thanks for the reply anyway

 

[pupuz]

Well, my story looks like far from over. About a week ago Home button stopped working, I've tried to reboot and got the black screen. With a lot of help here we've figured out that emuNAND was to to blame, corrupt or whatever. I've started over, formatted microSD to FAT32 and installed new emuMMC partition on it. Updated fw to 14.1.0, started copying via DBI, and after 3 games put on microSD I got write errors from DBI, then after restart - yellow panic 010041544D530000 error message from Atmosphere. Tried to eject the SD and figure out if I can check it for errors or format it - turned out Switch has made the card read-only, I can't format it on Wndows or a Mac, only errors. Does it mean the card is dead and if anything can be done at this point? It's Samsung EVO, bought via Samsung website, fake proof and considered reliable. Second week in despair.

I can't format this card, can't delete partitions, everything is "screaming" read-only and write error making the card unusable. What has possibly gone wrong?

 

[Dust2dust]

I can't format this card, can't delete partitions, everything is "screaming" read-only and write error making the card unusable. What has possibly gone wrong?

If you have tried everything and nothing works, I would just ultimately try to low-level format the SD card. If even that doesn't work, your SD card is good for the garbage bin.

edit: I noticed the tool is not linked on that page. It can be found here. Good luck!

 

[Klavice Gavin]

So anyway... a day ago I tried to load CFW on my V1 Switch but unfortunately it just sort of crashed and at first said "1bit mode " but then I tried to load it through another SD card and it worked fine on OFW anyway... This new SD card though is ungodly slow and what's more I had 260GB worth of games on my old SD card which all of a sudden decides not to read. I figure the problem might be my SD card reader as it said it wasn't seated but sometimes I jiggle the card around in it and it works flawlessly sometimes. I've tried to use different SD cards but now none of them work. I was never forceful with putting in my SD cards.

 

[pupuz]

If you have tried everything and nothing works, I would just ultimately try to low-level format the SD card. If even that doesn't work, your SD card is good for the garbage bin.

edit: I noticed the tool is not linked on that page. It can be found here. Good luck!

Got it, thanks! Found out I'm within Samsung 3-year warranty and just returned it. But now I'm uber-conspicious, if Switch/Hekate/Tegraexplorer/DBI can mess with any card on this level. It was pretty reliable, nice model of a solid brand, before enunand failed and I've begun trying to re-install everything.

 

[Dust2dust]

Got it, thanks! Found out I'm within Samsung 3-year warranty and just returned it. But now I'm uber-conspicious, if Switch/Hekate/Tegraexplorer/DBI can mess with any card on this level. It was pretty reliable, nice model of a solid brand, before enunand failed and I've begun trying to re-install everything.

You may have bought a lemon. It can happen with the best brands.

 

[ChanseyIsTheBest]

Is any console-specific data contained within Switch save files and is there any ban risk if someone else uses my save file? I'm asking this because I would like to upload save files of my games for others to use but I don't want my console to get banned if I do ever decide to go online eventually. I've never gone online at all on my Switch and don't have an actual Nintendo account (use Linkalo for the games that need it)

 

[binkinator]

Is any console-specific data contained within Switch save files and is there any ban risk if someone else uses my save file? I'm asking this because I would like to upload save files of my games for others to use but I don't want my console to get banned if I do ever decide to go online eventually. I've never gone online at all on my Switch and don't have an actual Nintendo account (use Linkalo for the games that need it)

Save files don’t have console specific information in them. That said you have to be careful w/ save files for Online games since unusual edits will be considered cheating so while you won’t get a ban for the console-specific data…the end result will be equally negative.

e: for example there are people who edit their ACNH saves successfully Online but they know EXACTLY what they are doing.

 

[Got_Famous06]

I accidentally updated switch to 15.0, I have updated atmosphere and sig patches, but when trying to install the new tinfoil update using DBI i get this https://imgur.com/5Y5KQIP, and the home screen looks like this https://imgur.com/ejXhUhT. Im 99% sure ive deleted everything on my sd card for old tinfoil. Does anyone have any clue what i could be doing wrong ?

 

[binkinator]

I accidentally updated switch to 15.0, I have updated atmosphere and sig patches, but when trying to install the new tinfoil update using DBI i get this https://imgur.com/5Y5KQIP, and the home screen looks like this https://imgur.com/ejXhUhT. Im 99% sure ive deleted everything on my sd card for old tinfoil. Does anyone have any clue what i could be doing wrong ?

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

Try using the self-installing tinfoil.nro file (put in /switch directory) from tinfoil.io and install using title override to start HBMenu.

Did you update your hekate?

If so do you still have:

kip1patch=nosigchk


…in your helate_ipl.ini?