Hacking SWITCH NOOB PARADISE - Ask questions here

[Zap2000]

Please read through what I'm saying as you're now forcing me to repeat myself. EmuNAND has no bearing on fuses since it cannot be booted into normally but with SX Loader which disables the fuse check. AutoRCM is only needed when SysNAND is running a firmware higher than the fuse count.

Also I was not aware of that issue (SX OS is really unstable). However this is a non-issue if you are not using AutoRCM since you do not need SX OS to boot OFW in that case.
If it has AutoRCM, then no. And you should be able to boot into recovery mode by holding volume + and - when using a payload that launches CFW/OFW. At the very least, I have confirmed its possible with ReiNX and ReiNX is the easiest to do this with since it autoboots into CFW.
Have you tried using another SD card?

Ok With the

Please read through what I'm saying as you're now forcing me to repeat myself. EmuNAND has no bearing on fuses since it cannot be booted into normally but with SX Loader which disables the fuse check. AutoRCM is only needed when SysNAND is running a firmware higher than the fuse count.

Also I was not aware of that issue (SX OS is really unstable). However this is a non-issue if you are not using AutoRCM since you do not need SX OS to boot OFW in that case.
If it has AutoRCM, then no. And you should be able to boot into recovery mode by holding volume + and - when using a payload that launches CFW/OFW. At the very least, I have confirmed its possible with ReiNX and ReiNX is the easiest to do this with since it autoboots into CFW.
Have you tried using another SD card?

If I keep my sysnand on 4.1.0 and update emuNAND on lastest fw 6.2 will I not get a black screen ? Not sure if I’m missing something? From reading known bugs in beta 2.4?

OFW 4.1 and lower support: These older firmwares require special care for backwards compatibility, and in this specific release if you use SX OS, your switch will boot to a black screen.
If you update your sysNAND this will be resolved for you. If you don't want to do that (day dreaming about the sloooowwwww booting dejavu exploit that will probably never be released) then you will have to wait for the next edition of SX OS for this to be fixed.

 

[TPMJB]

So...I dumped all the keys to my SD card using Hekate in 4.1, then install Choidujor to run 6.2. So far so good, but Lockpick couldn't get the tegra keys. So I rebooted into hekate and redumped my keys in hekate. Atmosphere wouldn't boot.

Weird...so I rebooted the console and now it won't boot hekate at all.

I have no idea what to do now.

Edit: I printed fuse info an kfuse info. I think I wasn't supposed to touch kfuse info

Edit2: Restored backups, all is working now. So glad I saved backups!

Edit3: Somehow my issue with dumping the Tegra keys is fixed now, which is why I went through this trouble to begin with. Well, hopefully I can install .csi files now.

 

[Draxzelex]

Yea ive tried three different ones, scan disk normal black one 32gb , scan disk ultra 32gb and another ultra but 64gb. I have tried doing a setup through SDsetup and selected reinx that way and does same. I did atmosphere but i keep getting the fusee secondary error.

Alright you may have a rare issue where your Switch doesn't detect payloads on the SD card as seen here.

Ok With the



If I keep my sysnand on 4.1.0 and update emuNAND on lastest fw 6.2 will I not get a black screen ? Not sure if I’m missing something? From reading known bugs in beta 2.4?

OFW 4.1 and lower support: These older firmwares require special care for backwards compatibility, and in this specific release if you use SX OS, your switch will boot to a black screen.
If you update your sysNAND this will be resolved for you. If you don't want to do that (day dreaming about the sloooowwwww booting dejavu exploit that will probably never be released) then you will have to wait for the next edition of SX OS for this to be fixed.

This warning applies to load OFW with SX OS V2.4. The logical conclusion would be to not load OFW with SX OS V2.4

 

[Zap2000]

Alright you may have a rare issue where your Switch doesn't detect payloads on the SD card as seen here.
This warning applies to load OFW with SX OS V2.4. The logical conclusion would be to not load OFW with SX OS V2.4

use SX OS, your switch will boot to a black screen

Alright you may have a rare issue where your Switch doesn't detect payloads on the SD card as seen here.
This warning applies to load OFW with SX OS V2.4. The logical conclusion would be to not load OFW with SX OS V2.4

Has any confirmed this? It didn’t mention OFW Just If use SX OS. Will sysnand on 4.1.0 it still be useful for me if it’s not loadable?

 

[Draxzelex]

use SX OS, your switch will boot to a black screen


Has any confirmed this? It didn’t mention OFW Just If use SX OS. Will sysnand on 4.1.0 it still be useful for me if it’s not loadable?

You do understand you can load OFW without SX OS right?

 

[Zap2000]

You do understand you can load OFW without SX OS right?

Ok I understand better know. Would the black screen boot coz any damage?

Why did they say If you update your sysNAND this will be resolved for you instead of
Don’t use sx ox to boot sysnand or OFW something?

What use would be from loading sysnand 4.1.0 anyhow?

 

[Draxzelex]

Ok I understand better know. Would the black screen boot coz any damage?

Why did they say If you update your sysNAND this will be resolved for you instead of
Don’t use sx ox to boot sysnand or something?

What use would be from loading sysnand 4.1.0 anyhow?

It shouldn't cause any damage but as long as you have a complete NAND backup (meaning boot0/boot1 and a rawnand.bin), you will be fine from 99% of all bricks.

The reason they say updating SysNAND would solve the issue is that some people boot OFW with SX OS and if V2.4 doesn't support firmwares 4.1 and below, aside from using another version of SX OS, you would use a firmware above 4.1

And the benefits of a SysNAND on 4.1 is being able to use the future warmboot exploit, Deja Vu, as well as any other exploits such as a theoretical untethered coldboot.

 

[rustb0y]

Alright you may have a rare issue where your Switch doesn't detect payloads on the SD card as seen here.
This warning applies to load OFW with SX OS V2.4. The logical conclusion would be to not load OFW with SX OS V2.4

Thank you for your help on this, just tried a Kingston 8gb sd card and boom all working on kosmos, ordered a 128gb sd now so happy days now I know which sd card works. Thanks again

 

[Zap2000]

It shouldn't cause any damage but as long as you have a complete NAND backup (meaning boot0/boot1 and a rawnand.bin), you will be fine from 99% of all bricks.

The reason they say updating SysNAND would solve the issue is that some people boot OFW with SX OS and if V2.4 doesn't support firmwares 4.1 and below, aside from using another version of SX OS, you would use a firmware above 4.1

And the benefits of a SysNAND on 4.1 is being able to use the future warmboot exploit, Deja Vu, as well as any other exploits such as a theoretical untethered coldboot.

Is it just me who wants sysnand on 4.1.0 they didn’t mention that u could keep it there and just update emuNAND weird
Are they not talking about ppl who want to boot cfw on sysnand 4.1.0?

Do u think I would be better using 2.0.1 stable and forgetting about emuNAND on beta ?
Or forget about keeping sysnand on 4.1.0?
Or is this way still my best setup chance?

 

[Draxzelex]

Is it just me who wants sysnand on 4.1.0 they didn’t mention that u could keep it there and just update emuNAND weird
Are they not talking about ppl who want to boot cfw on sysnand 4.1.0?

Do u think I would be better using 2.0.1 stable and forgetting about emuNAND on beta ?
Or forget about keeping sysnand on 4.1.0?
Or is this way still my best setup chance?

Most likely, yes.

And like I said earlier, eventually games and other content will require higher firmware such as 6.2 so you will need to use SX OS V2.4 or higher at some point. Who knows when they'll release a more stable update that works on firmwares 6.2 and higher.

 

[Zap2000]

Most likely, yes.

And like I said earlier, eventually games and other content will require higher firmware such as 6.2 so you will need to use SX OS V2.4 or higher at some point. Who knows when they'll release a more stable update that works on firmwares 6.2 and higher.

So what u think my best way available now is ? Wat would u advise to do?

 

[Draxzelex]

So what u think my best way available now is ? Wat would u advise to do?

There is no best way. That all depends on what you want to do and what you want to accomplish. This is also why many consider the Switch scene a mess because there is no definitive CFW like the 3DS scene for example.

 

[Zap2000]

There is no best way. That all depends on what you want to do and what you want to accomplish. This is also why many consider the Switch scene a mess because there is no definitive CFW like the 3DS scene for example.

Yeah defo took me longer to learn and thinking about the best way. I think that way above if it’s possible with sx os for now with easy way then I change to community down the road. On the emuNAND sx os wats the best method of running that? Just found out there was three different ways have they pros and cons?
Will I just use jtag and sleep mode for staying in cfw the way I’m going it?
Will I be able to get out of black screen if I do boot ofw by mistake ? And coz it’s lower firmware I won’t have blown any fuses.

 

[Draxzelex]

Yeah defo took me longer to learn and thinking about the best way. I think that way above if it’s possible with sx os for now with easy way then I change to community down the road. On the emuNAND sx os wats the best method of running that? Just found out there was three different ways have they pros and cons?
Will I just use jtag and sleep mode for staying in cfw the way I’m going it?
Will I be able to get out of black screen if I do boot ofw by mistake ? And coz it’s lower firmware I won’t have blown any fuses.

I'm not going to sift through 24 pages of the 2.4 release thread so my analysis is only limited to what their announcement says and what hexkyz has tweeted out.

The major difference between it being on the SD card and internal storage is that the SD card is far less detectable at the cost of taking up space on your card. Not sure what is the difference between partitioning your SD card and making a file but the former formats your SD card so if you're impatient, the latter seems like a shortcut.

Sleep mode is fine as long as the firmware you are running has a fuse count that either matches or exceeds it.

You can just perform a manual shutdown (holding power for 12 seconds) to get out of a black screen. This solves 99% of issues with booting the console on or off.

 

[Zap2000]

I'm not going to sift through 24 pages of the 2.4 release thread so my analysis is only limited to what their announcement says and what hexkyz has tweeted out.

The major difference between it being on the SD card and internal storage is that the SD card is far less detectable at the cost of taking up space on your card. Not sure what is the difference between partitioning your SD card and making a file but the former formats your SD card so if you're impatient, the latter seems like a shortcut.

Sleep mode is fine as long as the firmware you are running has a fuse count that either matches or exceeds it.

You can just perform a manual shutdown (holding power for 12 seconds) to get out of a black screen. This solves 99% of issues with booting the console on or off.

emuNAND as partition is that supported if I’m on ofw 4.1.0 someone msg me and told me not?

I'm not going to sift through 24 pages of the 2.4 release thread so my analysis is only limited to what their announcement says and what hexkyz has tweeted out.

The major difference between it being on the SD card and internal storage is that the SD card is far less detectable at the cost of taking up space on your card. Not sure what is the difference between partitioning your SD card and making a file but the former formats your SD card so if you're impatient, the latter seems like a shortcut.

Sleep mode is fine as long as the firmware you are running has a fuse count that either matches or exceeds it.

You can just perform a manual shutdown (holding power for 12 seconds) to get out of a black screen. This solves 99% of issues with booting the console on or off.

Someone msg me saying partitioning one not supported on OFW 4.1.0.?
Have u any steps and links for me to complete the process?

 

[TherealDarknes]

I don't really care about modding now but I want it in the future I found a "XAW1007900X" switch at a store is there any way to test if it's moddable after buying it without modding it

Oh and what is "blowing a fuse"

 

[steamcheapcom]

I am currently on 5.1.0. I would like to be able to play retail games, download games, and DLC. If possible I would like to be able to still go online in the future (with actual cartridges). I would like not to use a jig every single time I boot if possible. What are my best options for which OS to install? Am I still on a good firmware?

 

[Draxzelex]

emuNAND as partition is that supported if I’m on ofw 4.1.0 someone msg me and told me not?



Someone msg me saying partitioning one not supported on OFW 4.1.0.?
Have u any steps and links for me to complete the process?

This is the only tutorial for setting up EmuNAND that I have seen. And I have not tested SX OS EmuNAND (because I don't have a license) so I don't know what works and what doesn't.

I don't really care about modding now but I want it in the future I found a "XAW1007900X" switch at a store is there any way to test if it's moddable after buying it without modding it

Oh and what is "blowing a fuse"

https://gbatemp.net/threads/a-defin...atched-or-not-purchases-after-07-2018.512018/ and https://gbatemp.net/threads/faq-efuses.494404/ although some info is outdated in the second thread such as bypassing the fuse check.

I am currently on 5.1.0. I would like to be able to play retail games, download games, and DLC. If possible I would like to be able to still go online in the future. What are my best options for which OS to install?

The 100% best method of avoiding a ban is making a clean hack-free NAND backup, staying offline with all CFW/homebrew, restoring it prior to going online, then repeating the process. This works regardless of CFW as this method relies on Nintendo being unable to detect anything in RCM namely dumping and restoring the NAND. The next best method is using SX OS' EmuNAND to keep all CFW/homebrew away from SysNAND.

 

[steamcheapcom]

This is the only tutorial for setting up EmuNAND that I have seen. And I have not tested SX OS EmuNAND (because I don't have a license) so I don't know what works and what doesn't.
https://gbatemp.net/threads/a-defin...atched-or-not-purchases-after-07-2018.512018/ and https://gbatemp.net/threads/faq-efuses.494404/ although some info is outdated in the second thread such as bypassing the fuse check.
The 100% best method of avoiding a ban is making a clean hack-free NAND backup, staying offline with all CFW/homebrew, restoring it prior to going online, then repeating the process. This works regardless of CFW as this method relies on Nintendo being unable to detect anything in RCM namely dumping and restoring the NAND. The next best method is using SX OS' EmuNAND to keep all CFW/homebrew away from SysNAND.

Thanks, so with those methods would I need to use a jig every time I boot to access CFW? With the SX OS option, would I be able to go online, play whatever games/DLC (CFW or not), etc., as long as I did not go online with a CFW game? Is it easy to avoid doing that?

--------------------- MERGED ---------------------------

Thanks, so with those methods would I need to use a jig every time I boot to access CFW? With the SX OS option, would I be able to go online, play whatever games/DLC (CFW or not), etc., as long as I did not go online with a CFW game? Is it easy to avoid doing that?

Also if I decided to just backup my NAND, hack my console, and stay offline forever (until I wanted to switch it back some day to sell the console), what OS is my best option?

 

[Draxzelex]

Thanks, so with those methods would I need to use a jig every time I boot to access CFW? With the SX OS option, would I be able to go online, play whatever games/DLC (CFW or not), etc., as long as I did not go online with a CFW game? Is it easy to avoid doing that?

AutoRCM can remove the need for a jig but you would need to be mindful that shutting down the Switch from CFW/OFW with AutoRCM enabled causes it to reboot into RCM instead of turning off which drains battery at a rate of 5% per hour. To shut down a console with AutoRCM, you have to power it down from RCM.

With SX OS, the purpose of EmuNAND is to conduct all manner of CFW and homebrew there while staying 100% offline and going online with SysNAND without touching CFW or homebrew. SysNAND and EmuNAND do not communicate with each other whatsoever.