Hacking SWITCH NOOB PARADISE - Ask questions here

Draxzelex · Mar 8, 2021

SoneaSunshine said:
Just tried the repair funtion, but also blackscreen -.- .
After formating my sdcard yesterday, I created a new emuMMC with hekate because I had the mood to do "everything new" xD to make it work again ^^ did not even tried to migrate my old sxos emuMMC Im not really sure about how the whole emuMMC thingi works, but i have a backup of my nand (clean nand backup before installing sxos) not of my emunand. the situation that I probably have the same problem with sxos and now atm (with new created emuMMC) and even when trying to boot undocked (!) is making me so unsureif its a bigger Problem here (sd card reader maybe ?). Sorry noob here -.-

Would it be okay if I create a new threat for my Problem since it seems not easiest thing to solve ?

I see no reason why you can't but maybe the SD card is fake. Did you ever try verifying it with a program such as h2testw?

Ashir said:
Hi guys, it's me again.

I updated my emuNAND to 11.0.1 with daybreak, choose install, select the folder with the fw update, wait for the update check, check ok, select continue, select preserve, select FAT32 + exFAT32, select continue, the install wnet without errors and select reboot.

After reboot I got a nice error (Error Code: 2162-0002 (0x4a2)), I google it and find out it was caused by custom thermes, I delete the folder /atmosphere/contents/0100000000001000 and now I ha an ever more nicer error 2001-0123 (0xf601), wich I don''t know how to fix.

Please help!

EDIT

Forget it, I fix it deleting the sysDVR folder (/atmosphere/contents/00FF0000A53BB665) but now I wonder:

I will not be able to use sysDVR now?

I will not ne able to use my old themes?

Its possible you may need to download the latest sysDVR if you haven't done so already. If you did already download the latest, it might not be compatible with firmware 11.0.1 which should be brought up to the author
When a theme is made, it is made for that specific firmware. Therefore whenever you update, you have to make your theme again which makes it seem more like a hassle especially if you update your firmware constantly

Ashir · Mar 8, 2021

Draxzelex said:
I see no reason why you can't but maybe the SD card is fake. Did you ever try verifying it with a program such as h2testw?

Its possible you may need to download the latest sysDVR if you haven't done so already. If you did already download the latest, it might not be compatible with firmware 11.0.1 which should be brought up to the author

When a theme is made, it is made for that specific firmware. Therefore whenever you update, you have to make your theme again which makes it seem more like a hassle especially if you update your firmware constantly

Yeah, sysDVR was updated to v5.1 to be compatible with fw 11.0.1, and I also update the theme installer, apparently fw 11.0.1 adds a new button and it needs to be removed with the new version of the theme installer for themes to work on 11.0.1. Live and learn I guess. Thank you for the help @Draxzelex

SoneaSunshine · Mar 8, 2021

SoneaSunshine said:
Thx tried but also blackscreen, I made a quick Vid with my phone If you want to take a look

Draxzelex said:
I see no reason why you can't but maybe the SD card is fake. Did you ever try verifying it with a program such as h2testw?

I just tested with H2testw, everything fine with my sdcard, no fake ... also installed a game on sdcard a few hours ago in OFW and it worked/played just fine and tired out other sd card yesterday without emuMMC just Atmosphere, same blackscreen

If there is no Hardware Problem since OFW is working, no sdcard Problem, and probably no SDcard-reader Problem (because blackscreen even without sdcard inside on OFW, when not docked while turning on) what else can it be

?

Can it be a (sys)nand problem ? Even if OFW is working ? (but hey it starts only docked and with the power and +, so maybe my problem is here.. ) just a bit worried since my clean sysnand Backup is old with low FW but If this would be a solution I would restore it ...

Draxzelex · Mar 8, 2021

SoneaSunshine said:
I just tested with H2testw, everything fine with my sdcard, no fake ... also installed a game on sdcard a few hours ago in OFW and it worked/played just fine and tired out other sd card yesterday without emuMMC just Atmosphere, same blackscreen

If there is no Hardware Problem since OFW is working, no sdcard Problem, and probably no SDcard-reader Problem (because blackscreen even without sdcard inside on OFW, when not docked while turning on) what else can it be ?

Can it be a (sys)nand problem ? Even if OFW is working ? (but hey it starts only docked and with the power and +, so maybe my problem is here.. ) just a bit worried since my clean sysnand Backup is old with low FW but If this would be a solution I would restore it ...

Just for the sake of trying, try booting Atmosphere using DeepSea

GerbilSwimmingPool · Mar 8, 2021

Draxzelex said:
I mean there's not much to explain. All you do is adhere to the normal rules when it comes to trading Pokemon which I assume requires both consoles to be on the same firmware using whatever methods are available to you. Hacking has no affect on local trading if that's what you assume.

Cool. Much appreciated.

Purple_Heart · Mar 8, 2021

BigOnYa said:
Seems like it's an easy fix, and only $15 for part. Make sure you have/order a tri-point Y00 screwdriver also. Good luck!

i already have tools for my switch ....and these repairshops here are shit.....i once asked if they can repair my switch.....no only xbox and ps......every store here is like that.......

Laraid · Mar 8, 2021

Tried reading the FAQ but I couldn't find a simple answer that I could understand. If I turn on my Switch without using Hekate/emuMMC can I play online without getting banned?

Draxzelex · Mar 8, 2021

Laraid said:
Tried reading the FAQ but I couldn't find a simple answer that I could understand. If I turn on my Switch without using Hekate/emuMMC can I play online without getting banned?

Going online after using any CFW/homebrew without a clean eMMC backup will risk a ban regardless of the CFW and/or homebrew applications uses. The only way to play online without getting banned is to avoid using any homebrew or CFW.

Laraid · Mar 8, 2021

Draxzelex said:
Going online after using any CFW/homebrew without a clean eMMC backup will risk a ban regardless of the CFW and/or homebrew applications uses. The only way to play online without getting banned is to avoid using any homebrew or CFW.

I see. I recall doing the whole SD partition for the emuMMC so I thought I also had an option of running the original stock one that doesn't have any CFW.

SoneaSunshine · Mar 9, 2021

Draxzelex said:
Just for the sake of trying, try booting Atmosphere using DeepSea

I did, and i get a nice deep sea screen and then Blackscreen again, same as with atmosphere and sxos -.- what makes me wonder is when i got the blackscreen and I press power again my swich tries to boot normal in OFW I see nintendo logo then blackscreen again. Only Way to boot it is in docking station holding power and pressing + till It boots in OFW ... I really cant see what the hell my switch´s problem is -.- thanks again @Draxzelex , do you think a faulty (sys)nand could do this ? even if OFW is working fine once it booted? btw I never used AutoRCM could this help me somehow to boot in atmos ? ^^

nevdee · Mar 9, 2021

BigOnYa said:
https://gbatemp.net/threads/emutool...r-sd-switch-emu-type-on-sxos-and-more.550756/

https://gbatemp.net/threads/tutorial-from-sx-os-to-atmosphere.533337/

Thanks for your help, managed to set up from scratch again with a new SD card.

Question is I went to check the version of my emuNand and it tells me there is a system update ready, how do I get rid of this?

I think my emuNAND is on a old version and I imagine I need to update?

on atmosphere do you use choidujour or is it a different app to use to update?

EDIT - Never mind For future ref looks like you can use Goldleaf to do this

Raiku · Mar 9, 2021

Hi,

I'm a big Noob in the Switch scene so I have some questions. Sorry for my bad english..

That's what I have at this moment:
- A Nintendo Switch Lite 9.0.1 + Micro SD 256GB (new) + Micro SD 16GB + SX Lite (new/uninstalled)

However, I have a few other questions about things I would like to ask you:

1 - Considering the Micro SD 256 GB is new, the Switch Lite asks me to update Switch Lite to 11.0.1 for use it, should I use the 16 GB MicroSD first, and transfer my data to Micro SD 256GB after Jailbreak?

2 - Can I install the 256GB MicroSD without upgrading my Switch Lite?

3 - The Switch Lite that once the MicroSD is installed will be upgraded to 11.0.1, can I still solder the SX Lite or is it dead?

4 - The Xecuter site being Down, how do I update the SX Lite? Because I saw that there is a micro usb plug with the chip, I guess it's used for Updates.

5 - Once the SX Lite chip is soldered, what tutorial should I follow to jailbreak my Switch Lite? Knowing that I don't want the SX OS because for me the Xecuter team is dead and buried as their site has been down for weeks, is there any other alternative ?

For the soldering, no problem, I know how to do it and I have all the necessary hardware (flux, etc.). But it's just that I'm confused and I don't know where to begin, because there are so many tutorials that I'm very lost, it's been a week that I've been doing research and I've seen different videos on Youtube, too much information kills information, especially since we don't know that they are the methods that are outdated or still valide.

Draxzelex · Mar 9, 2021

SoneaSunshine said:
I did, and i get a nice deep sea screen and then Blackscreen again, same as with atmosphere and sxos -.- what makes me wonder is when i got the blackscreen and I press power again my swich tries to boot normal in OFW I see nintendo logo then blackscreen again. Only Way to boot it is in docking station holding power and pressing + till It boots in OFW ... I really cant see what the hell my switch´s problem is -.- thanks again @Draxzelex , do you think a faulty (sys)nand could do this ? even if OFW is working fine once it booted? btw I never used AutoRCM could this help me somehow to boot in atmos ? ^^

If OFW works fine, then it cannot be an eMMC issue. If you cannot boot anything from the SD card, then it might be either an issue with the SD card itself or the SD card reader which are both hardware issues. Either way, I'd also recommend making your own thread to hear other people's opinions.

Raiku said:
Hi,

I'm a big Noob in the Switch scene so I have some questions. Sorry for my bad english..

That's what I have at this moment:
- A Nintendo Switch Lite 9.0.1 + Micro SD 256GB (new) + Micro SD 16GB + SX Lite (new/uninstalled)

However, I have a few other questions about things I would like to ask you:

1 - Considering the Micro SD 256 GB is new, the Switch Lite asks me to update Switch Lite to 11.0.1 for use it, should I use the 16 GB MicroSD first, and transfer my data to Micro SD 256GB after Jailbreak?

2 - Can I install the 256GB MicroSD without upgrading my Switch Lite?

3 - The Switch Lite that once the MicroSD is installed will be upgraded to 11.0.1, can I still solder the SX Lite or is it dead?

4 - The Xecuter site being Down, how do I update the SX Lite? Because I saw that there is a micro usb plug with the chip, I guess it's used for Updates.

5 - Once the SX Lite chip is soldered, what tutorial should I follow to jailbreak my Switch Lite? Knowing that I don't want the SX OS because for me the Xecuter team is dead and buried as their site has been down for weeks, is there any other alternative ?

For the soldering, no problem, I know how to do it and I have all the necessary hardware (flux, etc.). But it's just that I'm confused and I don't know where to begin, because there are so many tutorials that I'm very lost, it's been a week that I've been doing research and I've seen different videos on Youtube, too much information kills information, especially since we don't know that they are the methods that are outdated or still valide.

No. Not only do you not need to update to use the SD card, if you update to 11.0.1, you will no longer be able to use the SX Lite. Format the SD card to FAT32 so you do not have to update the firmware
I don't understand your question. You do not "install" SD cards
The SD card has no affect on the SX Lite
I believe there is a way for the CFW to update itself once you are inside but you shouldn't rely on the site for updates due to the recent arrests. I hear TX has a Discord server where they post updates but I do not know how to locate it
I recommend following this guide

feauxtiger · Mar 10, 2021

So I goofed tonight. LOL. I was wanting to mess around with Amiibo stuff and decided to see if Tinfoil had any of them. I am using Hekate to launch Atmosphere. I know Tinfoil doesn't play nice with it, but I used Cling Wrap the other day to successfully grab an update I couldn't get elsewhere so I tried using Tinfoil again. Tinfoil wouldn't launch so I decided to reboot my Switch, but stupid me didn't think about the fact I'd used Cling Wrap to rename folders, so my SD card tried to launch with the renamed folders (bootloader) and (atmosphere/kips) (it didn't work).

I tried renaming the files using my PC, but I think I messed something up with Hekate when I did that. RCM still works so I launched into fusee primary to try and resolve the naming issue. I was able to get into Atmosphere to delete the folders Cling Wrap renamed (using Goldleaf) and deleted the hekate file in the renamed b00tloader file that Cling Wrap created. I then tried to relaunch using Hekate.

The Hekate payload successfully launches, but when I click the "Launch" option from the Hekate menu, it says there are no configurations there (I don't remember the exact wording, but I can try and update this once my SD card is finished backing up). I'm currently backing up my entire SD card so I hopefully don't mess anything else up any worse than I have.

I think what is happening is that when I launch Hekate it's not able to see the emummc I have been using, even though it's on the SD card. I compared the original Hekate folder I got from this forum's homebrew setup link and the config file is different than what I currently have on my SD card. The config for hekate_ipl from the software package I got from the guide is as follows:

[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee-primary.bin

The config for the hekate_ipl currently on my card is as follows:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

I'm not too tech savvy, but the main differences I see are that the config on my SD card right now has bootprotect=0 listed and the config on my SD card is also missing the text at the bottom that seems to point to the boot options (CFW sysMMC, CFW emuMMC, etc.)

I can browse my SD card and see the emuMMC folder, so I guess that's a positive sign, but I have no idea how to get Hekate to launch into it from the Hekate menu. When I load fusee primary from the Hekate payloads option I can get into atmosphere but none of my backups are working. I do know that Cling Wrap also renames the atmopshere/kips folder, so maybe it has something to do with that?

UPDATE 1: I just moved the hekate ini file from the sigpatch update to my SD card and it's now displaying emuMMC in the launch spot, but I'm getting a corrupt data error. Should I just reinstall all my backups that have the error message? There's a little exclamation point above several games. I used the updated sig patch data, so I guess the best solution is just to reinstall?

UPDATE 2: I ran the check for corrupted data and a couple game said "corrupted data found" and prompted me to redownload. When I tried launching the games after that, they worked.

Looks like my issue is resolved, except for Amiibo stuff. Just wanted to leave this post up in case anyone wants to explain what likely happened in so I don't make the same mistake again. MODS: if you want to delete the post, please feel free to do so.

I'd be eternally grateful for some help with this. I hope the solution is as simple as clicking a restore emuMMC button in Hekate, but I'm not too sure. Thanks in advance for your help and patience!

GerbilSwimmingPool · Mar 10, 2021

Draxzelex said:
I mean there's not much to explain. All you do is adhere to the normal rules when it comes to trading Pokemon which I assume requires both consoles to be on the same firmware using whatever methods are available to you. Hacking has no affect on local trading if that's what you assume.

Thanks for the help, man. It's much appreciated. Bought the Switch and currently waiting on it to ship. I think I got an amazing deal on it as well.

Quick questions, I know this probably have been asked way too many times. What would you guys recommends for SD card size? 128gb, 256gb, larger on unpatched Switch?

Are there any precautions that I can take to not get myself banned other than keeping my device without a wifi connection?

Any cool or interesting homebrew software that is a must have? Wireless streaming, Doom, or custom wallpaper... I'm not sure what is possible as I am just diving in now. Thank you!

Draxzelex · Mar 10, 2021

feauxtiger said:
So I goofed tonight. LOL. I was wanting to mess around with Amiibo stuff and decided to see if Tinfoil had any of them. I am using Hekate to launch Atmosphere. I know Tinfoil doesn't play nice with it, but I used Cling Wrap the other day to successfully grab an update I couldn't get elsewhere so I tried using Tinfoil again. Tinfoil wouldn't launch so I decided to reboot my Switch, but stupid me didn't think about the fact I'd used Cling Wrap to rename folders, so my SD card tried to launch with the renamed folders (bootloader) and (atmosphere/kips) (it didn't work).

I tried renaming the files using my PC, but I think I messed something up with Hekate when I did that. RCM still works so I launched into fusee primary to try and resolve the naming issue. I was able to get into Atmosphere to delete the folders Cling Wrap renamed (using Goldleaf) and deleted the hekate file in the renamed b00tloader file that Cling Wrap created. I then tried to relaunch using Hekate.

The Hekate payload successfully launches, but when I click the "Launch" option from the Hekate menu, it says there are no configurations there (I don't remember the exact wording, but I can try and update this once my SD card is finished backing up). I'm currently backing up my entire SD card so I hopefully don't mess anything else up any worse than I have.

I think what is happening is that when I launch Hekate it's not able to see the emummc I have been using, even though it's on the SD card. I compared the original Hekate folder I got from this forum's homebrew setup link and the config file is different than what I currently have on my SD card. The config for hekate_ipl from the software package I got from the guide is as follows:

[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee-primary.bin

The config for the hekate_ipl currently on my card is as follows:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

I'm not too tech savvy, but the main differences I see are that the config on my SD card right now has bootprotect=0 listed and the config on my SD card is also missing the text at the bottom that seems to point to the boot options (CFW sysMMC, CFW emuMMC, etc.)

I can browse my SD card and see the emuMMC folder, so I guess that's a positive sign, but I have no idea how to get Hekate to launch into it from the Hekate menu. When I load fusee primary from the Hekate payloads option I can get into atmosphere but none of my backups are working. I do know that Cling Wrap also renames the atmopshere/kips folder, so maybe it has something to do with that?

UPDATE 1: I just moved the hekate ini file from the sigpatch update to my SD card and it's now displaying emuMMC in the launch spot, but I'm getting a corrupt data error. Should I just reinstall all my backups that have the error message? There's a little exclamation point above several games. I used the updated sig patch data, so I guess the best solution is just to reinstall?

UPDATE 2: I ran the check for corrupted data and a couple game said "corrupted data found" and prompted me to redownload. When I tried launching the games after that, they worked.

Looks like my issue is resolved, except for Amiibo stuff. Just wanted to leave this post up in case anyone wants to explain what likely happened in so I don't make the same mistake again. MODS: if you want to delete the post, please feel free to do so.

I'd be eternally grateful for some help with this. I hope the solution is as simple as clicking a restore emuMMC button in Hekate, but I'm not too sure. Thanks in advance for your help and patience!

Your initial issue was caused by the hekate_ipl.ini file being modified but it is not clear how in your post. However that is not important. Honestly, you should step away from the fake "tinfoil" and use another title installer so that there is zero chance of this ever happening again. I highly recommend switching to TinWoo Installer instead.

GerbilSwimmingPool said:
Thanks for the help, man. It's much appreciated. Bought the Switch and currently waiting on it to ship. I think I got an amazing deal on it as well.

Quick questions, I know this probably have been asked way too many times. What would you guys recommends for SD card size? 128gb, 256gb, larger on unpatched Switch?

Are there any precautions that I can take to not get myself banned other than keeping my device without a wifi connection?

Any cool or interesting homebrew software that is a must have? Wireless streaming, Doom, or custom wallpaper... I'm not sure what is possible as I am just diving in now. Thank you!

Buy whatever size SD card you can afford. Some Switch games are smaller than 1 GB while others are over 20. It is hard for anyone to recommend you a size since they don't know a lot of things about you such as how many games you're willing to play, if you'll make room for more once you're done with some, or even the types of games you will play.

The only way to avoid getting banned is to not go online after using any CFW or homebrew. However you accomplish that is up to you.

Just like with the SD card size, it is hard to recommend homebrew applications that fit your personal needs since I don't know about your personal needs.

LraO · Mar 10, 2021

Hello everyone,

real noob here. I really tried to find the answer before asking here, I’m noob but not lazy. I bought my switch already running atmosphere emuNAND 10.0.4|AWS 0.12.0|E. I have 2 questions. How do I update so I can play the newest games? And second and I believe more complex. Can I switch my sdcard for a “bigger” one? I know I’ll have to setup the sdcard and then follow some other steps. My OFW is 4.1.0 so I already have access to pegascape to launch the CFW I’m using. Is it possible? I’m sorry for the poor English and the lack of knowledge.

Draxzelex · Mar 10, 2021

LraO said:
Hello everyone,

real noob here. I really tried to find the answer before asking here, I’m noob but not lazy. I bought my switch already running atmosphere emuNAND 10.0.4|AWS 0.12.0|E. I have 2 questions. How do I update so I can play the newest games? And second and I believe more complex. Can I switch my sdcard for a “bigger” one? I know I’ll have to setup the sdcard and then follow some other steps. My OFW is 4.1.0 so I already have access to pegascape to launch the CFW I’m using. Is it possible? I’m sorry for the poor English and the lack of knowledge.

You can update your firmware with homebrew applications such as ChoiDujourNX or Daybreak
Yes you can move all of your stuff to a bigger SD card. Since you are using emuMMC (partition-based presumably), I recommend following this guide for transferring your emuMMC. All of the other files and folders can be directly moved from one SD card to another

LraO · Mar 10, 2021

Alright, thanks. This update with ChoiDujourNX or daybreak is made directly on the console? I’m sorry again for the stupid question. I’m not sure if it’s a partition-based, how could I check that?

Draxzelex · Mar 10, 2021

LraO said:
Alright, thanks. This update with ChoiDujourNX or daybreak is made directly on the console? I’m sorry again for the stupid question. I’m not sure if it’s a partition-based, how could I check that?

The way both ChoiDujourNX and Daybreak work is that they install firmware files located on your SD card. Firmware files are copyrighted material however so you must track those down yourself. The easiest way to know if you're using partition or file based is by checking how much free space is on your SD card. If you notice you're missing about 30 GB of available space, then you are using partition based. If you have a file on your SD card that is about 30 GB but is not your eMMC backup, then you are using file based.

Hacking SWITCH NOOB PARADISE - Ask questions here

Well-Known Member

Member

Member

Well-Known Member

Well-Known Member

GBATemp´s weirdest Individual

Active Member

Well-Known Member

Active Member

Member

Member

New Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

New Member

Well-Known Member

Similar threads

Popular threads in this forum