Hacking Question what is the best scenario for brand new unpatched switch with firmware 4.1.0?

[Reecey]

@Goldenman66 Just to let you know I am giving all this information to you because I had another brand new switch myself about 8 months ago and it's official firmware is on 4.1.0 like yours I suggest you should take my advice don't use Atmosphere at all or it's emunand Also if you are thinking of using your emunand online like myself, certainly do not use Atmosphere! You will just get lost in your setup and you will end up with a banned switch. If you have already been using Atmosphere and trying to setup it's emunand and by the looks of your comments you already have done you might be too late..

 

[Goldenman66]

@Goldenman66 Just to let you know I am giving all this information to you because I had another brand new switch myself about 8 months ago and it's official firmware is on 4.1.0 like yours I suggest you should take my advice don't use Atmosphere at all or it's emunand Also if you are thinking of using your emunand online like myself, certainly do not use Atmosphere! You will just get lost in your setup and you will end up with a banned switch. If you have already been using Atmosphere and trying to setup it's emunand and by the looks of your comments you already have done you might be too late..

yes you are right i tried atmosphere but it didn't work and i'm going to try sxos now, any advice before going through?

 

[Goldenman66]

@Goldenman66 Just to let you know I am giving all this information to you because I had another brand new switch myself about 8 months ago and it's official firmware is on 4.1.0 like yours I suggest you should take my advice don't use Atmosphere at all or it's emunand Also if you are thinking of using your emunand online like myself, certainly do not use Atmosphere! You will just get lost in your setup and you will end up with a banned switch. If you have already been using Atmosphere and trying to setup it's emunand and by the looks of your comments you already have done you might be too late..

yes you are right i tried atmosphere but it didn't work and i'm going to try sxos now, any advice before going through?

 

[Goldenman66]

@Goldenman66 Just to let you know I am giving all this information to you because I had another brand new switch myself about 8 months ago and it's official firmware is on 4.1.0 like yours I suggest you should take my advice don't use Atmosphere at all or it's emunand Also if you are thinking of using your emunand online like myself, certainly do not use Atmosphere! You will just get lost in your setup and you will end up with a banned switch. If you have already been using Atmosphere and trying to setup it's emunand and by the looks of your comments you already have done you might be too late..

yes you are right i tried atmosphere but it didn't work and i'm going to try sxos now, any advice before going through?

 

[Goldenman66]

@Goldenman66 Just to let you know I am giving all this information to you because I had another brand new switch myself about 8 months ago and it's official firmware is on 4.1.0 like yours I suggest you should take my advice don't use Atmosphere at all or it's emunand Also if you are thinking of using your emunand online like myself, certainly do not use Atmosphere! You will just get lost in your setup and you will end up with a banned switch. If you have already been using Atmosphere and trying to setup it's emunand and by the looks of your comments you already have done you might be too late..

yes you are right i tried atmosphere but it didn't work and i'm going to try sxos now, any advice before going through? i need to be on the safe side while playing online and use the benefit of downloading free games too

 

[Reecey]

yes you are right i tried atmosphere but it didn't work and i'm going to try sxos now, any advice before going through?

Yes read my comment thoroughly on page 1, it’s the long one a bit further down the page, follow that. I cannot help much at the moment I’m out and using my phone but it should be fairly straight forward. Make sure like I did use the general 2.5.3 build first from the sxos page to back your nand up and setup emunand, not the 2.8 beta build. Once you have setup “hidden partition emunand” put all your files back onto your sd card including the 8.1.0 firmware files and boot back into your emunand, it should still be on firmware 4.1.0 make sure it says “emunand” in the album settings then go ahead update sxos through the sxos menu too build 2.8 and then use ChoiDujournx and update firmware 8.1.0 exfat. The firmware files are on the net just google it.

 

[Goldenman66]

Yes read my comment thoroughly on page 1, it’s the long one a bit further down the page, follow that. I cannot help much at the moment I’m out and using my phone but it should be fairly straight forward. Make sure like I did use the general 2.5.3 build first from the sxos page to back your nand up and setup emunand, not the 2.8 beta build. Once you have setup “hidden partition emunand” put all your files back onto your sd card including the 8.1.0 firmware files and boot back into your emunand, it should still be on firmware 4.1.0 make sure it says “emunand” in the album settings then go ahead update sxos through the sxos menu too build 2.8 and then use ChoiDujournx and update firmware 8.1.0 exfat. The firmware files are on the net just google it.

ok thanks a lot i'll try and send you the result

 

[Goldenman66]

Yes read my comment thoroughly on page 1, it’s the long one a bit further down the page, follow that. I cannot help much at the moment I’m out and using my phone but it should be fairly straight forward. Make sure like I did use the general 2.5.3 build first from the sxos page to back your nand up and setup emunand, not the 2.8 beta build. Once you have setup “hidden partition emunand” put all your files back onto your sd card including the 8.1.0 firmware files and boot back into your emunand, it should still be on firmware 4.1.0 make sure it says “emunand” in the album settings then go ahead update sxos through the sxos menu too build 2.8 and then use ChoiDujournx and update firmware 8.1.0 exfat. The firmware files are on the net just google it.

i tried to follow your advise and use sxos 2.5.3 but after emunand created successful it can't be enabled? also when i move sd card to pc i found two partitions one is un-allocated and another one is un-formatted, i don't know what i do next?

 

[Reecey]

i tried to follow your advise and use sxos 2.5.3 but after emunand created successful it can't be enabled? also when i move sd card to pc i found two partitions one is un-allocated and another one is un-formatted, i don't know what i do next?

Sounds just perfect!

It shows enabled as standard that’s what it should say, if you touch enabled it disables emunand don’t do this.

It formats your card after creating emunand that’s how it should be.

Yes that’s also correct one part is allocated that is your hidden partition the rest is yours you should see an emutendo folder put all your files back on your sd card and boot back into your 4.1.0 emunand go to the album just check it says emunand top right hand corner, then update sxos to 2.8 build you will see an option, then make sure you have the 8.1.0 firmware files on your sd card in a folder “8.1.0” start ChoiDujournx up under the homebrew tab and setup your 8.1.0 firmware. ChoiDujournx is very straight forward just select your “8.1.0” folder by touching it, then start firmware let it run it’s ok, it will thoroughly check everything out and let it reboot.

 

[Goldenman66]

Sounds just perfect!

It shows enabled as standard that’s what it should say, if you touch enabled it disables emunand don’t do this.

It formats your card after creating emunand that’s how it should be.

Yes that’s also correct one part is allocated that is your hidden partition the rest is yours you should see an emutendo folder put all your files back on your sd card and boot back into your 4.1.0 emunand go to the album just check it says emunand top right hand corner, then update sxos to 2.8 build you will see an option, then make sure you have the 8.1.0 firmware files on your sd card in a folder “8.1.0” start ChoiDujournx up under the homebrew tab and setup your 8.1.0 firmware. ChoiDujournx is very straight forward just select your “8.1.0” folder by touching it, then start firmware let it run it’s ok, it will thoroughly check everything out and let it reboot.

What i mean it is disabled and when I touch to enable it remains disabled and never got enabled? Also for sd card allocated and unformatted space is 90GB and the rest 29GB is unallocated

 

[Reecey]

What i mean it is disabled and when I touch to enable it remains disabled and never got enabled Also for sd card allocated and unformatted space is 90GB and the rest 29GB is unallocated

The sd card is correct that’s how it should be. I don’t understand why it says disabled? Sounds like you did everything correct to me have you put your files back onto your sd card 2.5.3 build and license after creating emunand? Did you format your sd card fat32 to begin with? Firmware 4.1.0 is only fat32 you need too update your emunand then to exfat 8.1.0. Try creating your emunand again delete format your sd card fat32 and create emunand again.

Edit: have you got an emutendo folder on your sd card?

 

[lordelan]

Edit: Marked things red that are very important to prevent fuse burning.

I wouldn't update sysNAND with ChoiDujourNX (since it's a homebrew).
If you want to play online with it either way, these would (have) be(en) the best steps:

1. NAND backup of your clean 4.1.0 FW
2. Update the official way (through system settings after setting up internet connection) to 8.1.0
3. Only if you want to prevent your fuse state (which is not needed imho):
   - Have a Jig and put it in as soon as the update starts
   - While it's going to reboot, hold VOL+ to get into RCM (to make sure not to miss the right time, already hold it while the update is almost finished!)
   - Use hekate, enable AutoRCM and boot stock sysNAND
4. Link your user profile to a Nintendo account if not already done
5. Put in 90DNS as primary and secondary in your internet connection
   
6. Reboot to RCM and use hekate to make another NAND dump
7. Copy your SD content to a temporary folder on your computer
8. Boot to RCM and fire up SX OS while holding VOL+ to get into SX OS boot menu
9. Create hidden partition based emuNAND from there
10. create sd:\emuMMC\emummc.ini on your SD card and paste the code I put at the end of this post
11. Copy back everything to the SD from your computer
    
12. Boot into CFW emuMMC from hekate (without changing any emuMMC settings there ... don't hit "migrate" or anything ... the emummc.ini already handles everything nicely
13. Reboot into stock sysNAND using hekate (your default payload for now! )
14. Remove 90DNS by setting DNS to automatic again
15. Have fun online on stock sysNAND and use everything else on CFW emuMMC

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

 

[tabzer]

I wouldn't update sysNAND with ChoiDujourNX (since it's a homebrew).
If you want to play online with it either way, these would (have) be(en) the best steps:

1. NAND backup of your clean 4.1.0 FW
2. Update the official way (through system settings after setting up internet connection) to 8.1.0
3. Only if you want to prevent your fuse state (which is not needed imho):
   - Have a Jig and put it in as soon as the update starts
   - While it's going to reboot, hold VOL+ to get into RCM
   - Use hekate, enable AutoRCM and boot stock sysNAND
4. Link your user profile to a Nintendo account if not already done
5. Put in 90DNS as primary and secondary in your internet connection
   
6. Reboot to RCM and use hekate to make another NAND dump
7. Copy your SD content to a temporary folder on your computer
8. Boot to RCM and fire up SX OS while holding VOL+ to get into SX OS boot menu
9. Create hidden partition based emuNAND from there
10. create sd:\emuMMC\emummc.ini on your SD card and paste the code I put at the end of this post
11. Copy back everything to the SD from your computer
    
12. Boot into CFW emuMMC from hekate (without changing any emuMMC settings there ... don't hit "migrate" or anything ... the emummc.ini already handles everything nicely
13. Reboot into stock sysNAND using hekate (your default payload for now! )
14. Remove 90DNS by setting DNS to automatic again
15. Have fun online on stock sysNAND and use everything else on CFW emuMMC

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

@Goldenman66 You need to answer a couple questions for the people helping you in this thread. Do you want to go online? Did you make a NAND backup before booting into cfw? If you didn't, that makes what everyone is saying about emunand/emummc is pointless for you.

 

[The Real Jdbye]

Do you care about playing online? If not, then there's probably no real reason to use an emuNAND.

If you don't care about online, keeping sysNAND on low firmware for the warmboot exploit is worth it. Though it's not much more convenient than RCM with a dongle, more options is always good.

 

[Goldenman66]

The sd card is correct that’s how it should be. I don’t understand why it says disabled? Sounds like you did everything correct to me have you put your files back onto your sd card 2.5.3 build and license after creating emunand? Did you format your sd card fat32 to begin with? Firmware 4.1.0 is only fat32 you need too update your emunand then to exfat 8.1.0. Try creating your emunand again delete format your sd card fat32 and create emunand again.

Edit: have you got an emutendo folder on your sd card?

i didn't got emutendo folder also i didn't but any thing on sd card after creating emunand attached sd card snapshot after creating emunand.

is this correct?

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

I wouldn't update sysNAND with ChoiDujourNX (since it's a homebrew).
If you want to play online with it either way, these would (have) be(en) the best steps:

1. NAND backup of your clean 4.1.0 FW
2. Update the official way (through system settings after setting up internet connection) to 8.1.0
3. Only if you want to prevent your fuse state (which is not needed imho):
   - Have a Jig and put it in as soon as the update starts
   - While it's going to reboot, hold VOL+ to get into RCM
   - Use hekate, enable AutoRCM and boot stock sysNAND
4. Link your user profile to a Nintendo account if not already done
5. Put in 90DNS as primary and secondary in your internet connection
   
6. Reboot to RCM and use hekate to make another NAND dump
7. Copy your SD content to a temporary folder on your computer
8. Boot to RCM and fire up SX OS while holding VOL+ to get into SX OS boot menu
9. Create hidden partition based emuNAND from there
10. create sd:\emuMMC\emummc.ini on your SD card and paste the code I put at the end of this post
11. Copy back everything to the SD from your computer
    
12. Boot into CFW emuMMC from hekate (without changing any emuMMC settings there ... don't hit "migrate" or anything ... the emummc.ini already handles everything nicely
13. Reboot into stock sysNAND using hekate (your default payload for now! )
14. Remove 90DNS by setting DNS to automatic again
15. Have fun online on stock sysNAND and use everything else on CFW emuMMC

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

i don't know it it good idea to update ofw to 8.1.0? i'm afraid that in the future i will need 4.1.0 for any reason

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

@Goldenman66 You need to answer a couple questions for the people helping you in this thread. Do you want to go online? Did you make a NAND backup before booting into cfw? If you didn't, that makes what everyone is saying about emunand/emummc is pointless for you.

yes i want to go online and yes i have a NAND backup before doing any thing also i didn't boot ever to CFW

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

If you don't care about online, keeping sysNAND on low firmware for the warmboot exploit is worth it. Though it's not much more convenient than RCM with a dongle, more options is always good.

do you mean if i need online i should update 4.1.0 firmware?

 

[tabzer]

If you want to preserve 4.1, use CFW and go online. You will need 2x Emunands/emummcs and not use your system nand.

 

[Goldenman66]

If you want to preserve 4.1, use CFW and go online. You will need 2x Emunands/emummcs and not use your system nand.

that what i'm trying to do

 

[tabzer]

@Reecey knows how to do it. He just hasn't said how, yet.

 

[lordelan]

i don't know it it good idea to update ofw to 8.1.0? i'm afraid that in the future i will need 4.1.0 for any reason

Why would you? If that thetherless coldboot exploit ever comes out? Highly doubt that but even when, if you follow my instructions and put in a Jig and hold VOL+ before the Switch automatically reboots after the official system update, you'll be in RCM where you fire up hekate and enable autoRCM. Your fuses are still fine then (4.1.0 state).
Updating the FW does not burn fuses. It's Ninty's bootloader that does so basically "booting without hekate" (or SX OS) burns fuses. Nothing else.

i didn't got emutendo folder also i didn't but any thing on sd card after creating emunand attached sd card snapshot after creating emunand.

is this correct?

That partition table is correct. The SX OS partition is hidden and will be displayed as unallocated in Windows. That's fine.
If you put the emummc.ini on your SD as I wrote above, it'll create the emutendo folder automatically when you use your emuMMC.

 

[Goldenman66]

Why would you? If that thetherless coldboot exploit ever comes out? Highly doubt that but even when, if you follow my instructions and put in a Jig and hold VOL+ before the Switch automatically reboots after the official system update, you'll be in RCM where you fire up hekate and enable autoRCM. Your fuses are still fine then (4.1.0 state).
Updating the FW does not burn fuses. It's Ninty's bootloader that does so basically "booting without hekate" (or SX OS) burns fuses. Nothing else.


That partition table is correct. The SX OS partition is hidden and will be displayed as unallocated in Windows. That's fine.
If you put the emummc.ini on your SD as I wrote above, it'll create the emutendo folder automatically when you use your emuMMC.

ok so i need to format second partition to exfat and create ini file as per your post then reboot into sxos and enable emunand right?

 

[The Real Jdbye]

that what i'm trying to do

Keep in mind that that's not 100% safe. You're still dealing with patched firmware, in essence CFW, even if you're treating the second emuNAND as a legit system, and especially with SX OS just the act of running it is enough to be flagged for a ban. Atmosphere should in theory be safer, and according to someone I asked in ReSwitched Discord, there is no way you can be banned simply for running Atmosphere, it's what you do with it that can get you banned. But despite what he said, in my mind there is always a risk, even if it's much smaller now than it was back when Hekate was first released.

 

[Reecey]

@Goldenman66
You going to have to start again. Erase your sd card to fat32 put your sxos files on your sd card 2.5.3 including your ChoiDujournx files you have to find the 4.1.0 firmware files google them again put those on your sd card boot up cfw as normal and update your 4.1.0 firmware through ChoiDujournx to exfat keep stealth on turn your Wi-fi off. I think this is your problem then once you’re on exfat then go back and setup emunand again. I think the fact your 4.1.0 ofw is fat32 still this is causing your issue some kind person can correct me but I’m sure this is your problem it’s not exfat 4.1.0 your still running fat32. @tabzer is this what I have missed out? It cannot be an autorcm issue because the latest ChoiDujournx build automatically turns autorcm on when flashing the firmware. Apart from what I have said I’m not sure what I am missing out on. I can only think it’s the fact his ofw 4.1.0 is fat32? and not exfat. I have already mentioned about the emutendo folder I just presumed he had created one and tried?

 

[tabzer]

I really don't know your method. When I play online, I play with a pure nand, completely unassisted by any cfw or bootloaders. I don't even use autorcm. When I want to do homebrew, I use a jig and payload. I'm just waiting for linux/lakka/android to be able to reboot to payload, which will significantly reduce how often I use a jig/external payload push. It seems @lordelan has more experience using both emunand and emummc. He has a hybrid situation it looks like. I'm reluctant about using emunand/emummc online. Personally I would stay with FAT32.