Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,157,303
  • Replies Replies 47,999
  • Likes Likes 66
I've been using 90DNS for some time now on my emuNAND, and I got no bans whatsoever, so I trust it. Yesterday I got an USB lan adapter and it is working on my Switch Dock (I tested on my "clean" sysNAND").

My noob question is: If I use 90DNS on the wired connection It will be as safe as for wifi networks?

(note that I am not using the dedicated router, all my settings are on the console itself)
 
I've been using 90DNS for some time now on my emuNAND, and I got no bans whatsoever, so I trust it. Yesterday I got an USB lan adapter and it is working on my Switch Dock (I tested on my "clean" sysNAND").

My noob question is: If I use 90DNS on the wired connection It will be as safe as for wifi networks?

(note that I am not using the dedicated router, all my settings are on the console itself)

You have to apply the DNS on the LAN (Wired Ethernet), same rules apply.
 
The error you get when launching pretty much explains the problem. If it asking you if Hekate or sept is updated then chances are they aren't. I also highly recommend following this guide instead.
Thanks for the reply. I have been using the latest versions of Hekate and Atmosphere. I just did the same thing with the "SD card" folder in the guide you linked and I get the same error.
 
Yes although by the sound of it, it doesn't seem like you did much of anything from that guide so I don't fear there is anything to overwrite.
So looking at the guide I did everything there already so I don't get why the SD card is apparently corrupted? It should be accessible because that's where emuMMC stuff goes, right?

Edit: I followed the guide and I guess the only thing that changed is that the SD is now called Switch SD lol but I guess the other SD that shows up is not suppose to be tampered with
 
Last edited by foreveryang,
Thanks for the reply. I have been using the latest versions of Hekate and Atmosphere. I just did the same thing with the "SD card" folder in the guide you linked and I get the same error.
How did you update Hekate and Atmosphere on your SD card?

So looking at the guide I did everything there already so I don't get why the SD card is apparently corrupted? It should be accessible because that's where emuMMC stuff goes, right?

I have emuMMC and it works as I am able to boot into Atmosphere...idk I'm just kind of dreading having to backup the SD card files again :sad:
Wait, if you already have an emuMMC, why are you partitioning your SD card then?
 
How did you update Hekate and Atmosphere on your SD card?

I've completely formatted my SD card and copied over the latest files from both githubs. I've also foratted and used the files from sdsetup. Results are the same with both.

Maybe I should try and older version since the NAND backup I restored is only FW 5.1.0?
 
I've completely formatted my SD card and copied over the latest files from both githubs. I've also foratted and used the files from sdsetup. Results are the same with both.

Maybe I should try and older version since the NAND backup I restored is only FW 5.1.0?
How is your SD card formatted?
 
I thought I had gotten CFW on Sysnand because the SD card keeps saying it needs to be formatted
Did you ever actually launch CFW though?

It was exFAT when the issue first happened (my NAND backup was one big file). Trying FAT32 formatted with Minitool Partition Wizard now and it's the same. It's a 400GB card.
Alright now I understand your issue after researching the error you posted and rereading your initial troubleshooting steps, particularly step 7. When you restored your backup, what exactly did you restore?
 
Alright now I understand your issue after researching the error you posted and rereading your initial troubleshooting steps, particularly step 7. When you restored your backup, what exactly did you restore?

I restored eMMC BOOT0 & BOOT1 and then eMMC RAW GPP according to this guide:

https://nh-server.github.io/switch-guide/extras/nandrestore/

The issue is that I thought my fuses weren't burned but it turns out they were. I'm pretty sure the NAND backup is from 5.1.0 and the fuses are burned to 9.0.
 
Did you ever actually launch CFW though?

Alright now I understand your issue after researching the error you posted and rereading your initial troubleshooting steps, particularly step 7. When you restored your backup, what exactly did you restore?

I entered Atmosphere and changed the theme so I don't get confused, that's all I did.
 
Last edited by foreveryang,
I restored eMMC BOOT0 & BOOT1 and then eMMC RAW GPP according to this guide:

https://nh-server.github.io/switch-guide/extras/nandrestore/

The issue is that I thought my fuses weren't burned but it turns out they were. I'm pretty sure the NAND backup is from 5.1.0 and the fuses are burned to 9.0.
Were the eMMC backup, BOOT0, and BOOT1 all on the same firmware version? Because the issue of the blue screen has nothing to do with fuses but rather a mismatch between your firmware and BOOT0/BOOT1; the fuses were never an issue if you were trying to boot from Hekate/fusee.

I entered Atmosphere and changed the theme so I don't get confused, that's all I did.
So did you ever verify that you actually booted into emuMMC?
 

Site & Scene News

Popular threads in this forum