Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,111,357
  • Replies Replies 47,954
  • Likes Likes 66
Ok. So this may not quite be a noob question. But it doesn't warrant a whole thread on its own.

I'm currently away with my brother. We both have modded switches. He hasn't gone incognito. I recommended this on his emunand. He went into tinfoil and did it. However he's also running exosphere.ini blanking the profinfo.

My question is has this done anything? Or has he just changed all the zeros to another load of zeros. I don't know if tinfoil can see through exosphere or not? I know it can identify different switches.... But I don't think it uses the serial?

I would put it in a pc and rename the exosphere file to check but can't until we get home.
Exosphere doesn't actually zero out the serial, it pretends to from the perspective of Nintendo. Meanwhile Incognito truly does zero out the serial which is why its no longer recommended to use since Incognito does the same job but much safer. Incognito can tell that the hardcoded serial isn't actually blank while exosphere is running so now its replaced the job of Incognito.
Guys where do I put the save file???
The save file for what? What are you trying to accomplish?
 
I wanted to check if Switch is banned or not, so I will delete CFW using Haku33, how do I know if Switch is banned or not?
Firstly, Haku33 does not "delete" CFW. It aggressively removes error codes and other pertinent information which can lead to a ban. In fact, a user has already been banned after usage of Haku33. Secondly, checking if a console has been banned or not is as simple as loading the eShop.
 
  • Like
Reactions: BigOnYa
Firstly, Haku33 does not "delete" CFW. It aggressively removes error codes and other pertinent information which can lead to a ban. In fact, a user has already been banned after usage of Haku33. Secondly, checking if a console has been banned or not is as simple as loading the eShop.
So how can I delete CFW? I'm going to check Switch are banned or not later.
 
Exosphere doesn't actually zero out the serial, it pretends to from the perspective of Nintendo. Meanwhile Incognito truly does zero out the serial which is why its no longer recommended to use since Incognito does the same job but much safer. Incognito can tell that the hardcoded serial isn't actually blank while exosphere is running so now its replaced the job of Incognito.

The save file for what? What are you trying to accomplish?
So how can I delete CFW? I'm going to check Switch are banned or not later.

If you don't have a clean nand backup. Don't boot ofw or try and factory reset or clean yourself. Follow this https://www.cfwaifu.com/haku33/

Make a backup first. Overwrite with the clean backup after.... And hope for the best.
Post automatically merged:

Guys where do I put the save file???
What save file? If your tranfering from one system to another put it in whatever folder your save manager made in the original system then press restore or inject instead of backup.
 
Exosphere doesn't actually zero out the serial, it pretends to from the perspective of Nintendo. Meanwhile Incognito truly does zero out the serial which is why its no longer recommended to use since Incognito does the same job but much safer. Incognito can tell that the hardcoded serial isn't actually blank while exosphere is running so now its replaced the job of Incognito.

I've a basic understanding of how they both work. I use both. Might seem overkill but I have a banned switch because an emunand.txt file became corrupt once (file read as 0 bytes). I have another switch not banned.

I simply suggested to my brother in holiday to use more than one level of protection. Because he already had tinfoil installed the easiest way was to use the built in incognito option and job done (in theory).

However it's showing the serial as all zeros before and after. So has using this actually done anything?

I've told him to airplane mode and rename exosphere.ini to check when he gets home. But if you know please share the knowledge.
Post automatically merged:

Actually it was sysmmc.txt I was trying to keep a clean nand. But using cfw for a faster boot.... It worked for about a year but did eventually result in a ban.
 
Hello everyone. I am looking for advice on how to unbrick my Switch after updating the stock firmware.

My Switch is unpatched and I can enter RCM using a jig. I was on firmware 10.1.0 before the update. I followed the NH Switch Guide on a previously unhacked Switch, including dumping my keys and creating backups. However, once I tried to launch Atmosphere, I'd only get thrown back into RCM.

My thought process at the time was that my firmware needed to be newer to match up with the latest Atmosphere. So I booted back into the stock firmware and updated. The dialog said it was successful and that the Switch would reboot, but it did not turn back on. So somehow, my Switch got bricked doing the official update. I tried the standard things such as holding the power button for 15sec (and in combination with the volume buttons), but no luck. In case it is somehow relevant, I should mention that my Switch does not have a working game card reader.

Getting back into Hekate, I tried the three launch options (Atmosphere emuNAND, Atmosphere sysNAND, and stock), but all blackscreened. Inside Hekate, I saw that the burnt fuse count had increased from 13 to 18 (firmware 16.0.0+), meaning that the update had been applied to a point.

Next I tried a guide entitled "Rectify Boot Errors" by Switchway to try to restore the system, but this did not work. I next tried to restore my backup (from before the update), but the Switch still does not boot. I stopped at this point as it was clear that I am out of my depth and might cause even further damage, which why I am turning to you folks.

I'd like to get back to a point where I can boot the stock firmware. Any help would be appreciated!
 
Last edited by switcher4579,
Hi all. I've done a lot of reading and i have a few questions if that's ok.

So there's 2 methods, CFW through unpatched console. Then there's modchip that them allows you to install CFW. right?

From what i understand the modchip simply allows you to install CFW, so the installation of CFW after installing the chip is the same as doing it on a unpatched console right?

I'm looking to buy the hwfly v5 or 4.1? This is where in really confused. I have one switch and one switch lite that i want to do I'm not sure which is the right one. I saw there's an instinct modchip too. It's that compatible with all versions or just oled?
 
I next tried to restore my backup (from before the update), but the Switch still does not boot. I stopped at this point as it was clear that I am out of my depth and might cause even further damage, which why I am turning to you folks.
Restoring your backup, like you did, should get you back to a working state, but the problem you have now is that your fuses count does not match your firmware. Solution: boot through Hekate. It ignores the burnt fuses. You should boot back to the same firmware you had when you made your backup. If everything is working, just re-hack and re-update afterwards.
 
Hmm, exactly the same way you installed the games in the first place. Through shops, or directly downloading the update as a nsp file and installing it.
Which shops? It's quite a painful task to look fot updates for each game for the matching region and manually install it.
 
Which shops? It's quite a painful task to look fot updates for each game for the matching region and manually install it.
Shops are just a source. If you don't know about them, don't worry about it. Wherever you found your games files (nsp or nsz files), you should also find the corresponding updates. Update files share the same gameid as the base files, except they end with 800 instead of 000, if I recall correctly, so that takes care of the matching region problem you mentioned.
 
Shops are just a source. If you don't know about them, don't worry about it. Wherever you found your games files (nsp or nsz files), you should also find the corresponding updates. Update files share the same gameid as the base files, except they end with 800 instead of 000, if I recall correctly, so that takes care of the matching region problem you mentioned.
Thank you, I knew about this but often I dont find recent updates... I thought there was another way such as updating them OTA or some website with game update compilation.
 
Thank you, I knew about this but often I dont find recent updates... I thought there was another way such as updating them OTA or some website with game update compilation.
Unless things have changed since I last checked, updates are usually becoming quickly available once they are released, on the different websites offering nsp files. I would google the gameid if I were you. Remember to end the gameid with 800 to specifically look for the update.
 
  • Like
Reactions: KarimPolska
Restoring your backup, like you did, should get you back to a working state, but the problem you have now is that your fuses count does not match your firmware. Solution: boot through Hekate. It ignores the burnt fuses. You should boot back to the same firmware you had when you made your backup. If everything is working, just re-hack and re-update afterwards.
You're right, I can boot into the older stock firmware using Hekate after restoring the backup. However, I'm confused as to where to go from here. As I noted, at the time I made the backup, Atmosphere didn't work for me, and it still doesn't. I even deleted the relevant files from my SD card and followed the guide again, but trying to launch puts me right back into RCM. I even tried obtaining older matching versions of Atmosphere/Hekate but those came with their own errors. I tried updating from within stock, but this just bricked that again and had to restore the backup. Any idea how I can get Atmosphere working? I really appreciate your help so far!
 

Site & Scene News

Popular threads in this forum