And Thanks again... my switch wouldnt go pass the nc logo in ofw and sysmmc mode... i rebuild my nand with this perfect video.. And everything is working again.. thnx for your hard work and this amazing video :)
Great video. It worked for me to perform a test, my oled switch does not dump the nand nor create emunand, however I managed to separately dump all the partitions except "SYSTEM" and "USER", so with your method I created my Donor nand, and with this nand I created my "emunand", after several errors and attempts I managed to boot the emunand, however after some time the console crashes and it takes a long time to enter the emunand again. I probably have a physics error in my physical nand module.
great tutorial as usual THANKS a question, what tutorial should I follow if I don't have any nand files, maybe I only have the PROD.KEYS, the nand is bad
@@braianmanueljoaquinleonor9380 u can fix that by reinstalling the game and updating the sigpatches (latest HATS pack has them). U don’t need to reinstall the nand for that
there is no method available to remove the ban from the nintendo switch, advice for life: next time be more careful and set up all the necessary defenses to avoid the ban
Excellent video! Thanks, one more switch saved from brick. Any idea why Console Serial number is XAW1000000000? after unbrick? I boot to ofw with no SD inside (unpatched).
After completing the procedure without errors, when I start CFW SysNand I see the Atmosphere logo and then the screen remains black. If I try to start OFW instead, I see the Nintendo logo and then the screen remains black. The crazy thing is that if I try to create the emuMMC and start it the emuMMC works perfectly
Hi, I have a problem with a friend's Switch, he used SYSNAND all this time, even though he had EMUMMC installed, his SYSNAND got corrupted and he can no longer use OFW, but the EMUMMC boots normally and can be used. Can I make a copy of the EMUMMC and transfer it to the EMMC? Please help me, I am using a translator to write this
Hello, friend, thank you very much for making your time and experience available on the subject... I have an OLED that when I insert a game card or connect it to the internet gives error 2123-0011, but only on the ORIGINAL system, would there be a solution? The unlocking system works normally.
@@sthetixofficial In the original system, after a few seconds with the game card or when I connect to the internet via Wi-Fi, I get the error 2123-0011. The following message: Error code: 2123-0011 Press the POWER button and restart the console [...] (X1) XAW1000000000 (X2) 18.1.0
hey. i have a question, after restoring BCPKG files, pops up EMMC is initialized in slower mode , well i hit ok and then follow your guide, when i hit launch, atmosphere launches, and stays black screen without nintendo logo without anything, do you know anything about this? some help ?
Does this fix empty partition table? I have all the keys from donor that I had fixed a few days ago but I accidently removed the rawnanad on Hekate and only left with the other files
I had problems with crashes. V1 model unpatched. Error code 2162-0002 (0x4a2). I couldn't find any solution so I decided to try to unbrick it. I did the level 1 with no success. Then i tried the level 2. Now things are even worse. When I choose to install the sysMMC or the stock ofw switch won't boot up and stays in black screen without even show atmosphere or switch logo. I don't know if it matters but I used the latest firmware 18.1.0 but in hekate in console information it says 17.0.0.
need some help here: got a oled and a v2 bugging out not booting ofw/sysnand (stuck at switch logo or giving 2002-3540 error), emunand boots without problem *the oled i'm having this problem since last week and haven't been able to fix it without removing the chip (removing the chip makes the console boot without problems, already changed the chip and the flats/wires 3 times so i dont believe they are the issue), if i restore a donor nand or the emummc to the emmc it gives a emmc error(slower mode) after is done and corrupts (purple/blue screen) *the v2 i just installed the chip a few moments ago and it bugged after creating the emunand (used a nxcore so is not a solder joint problem as it just has the soldering on the nvidia chip) *restoring only the boot0/boot1 to the emmc on the v2 and on the oled seems to "wipe" the emmc contents (emmc in slower mode and partition table is empty)
Hi sir i need your help please, i have v2 with firmware 17.01 using hats pack, everything is fine until i boot into ofw to factory reset and online update firmware, but both give me an error and was not successful, then my switch cannot boot into ofw anymore. Today i follow this video to rebuild sysnand to v18. 01 using my backup keys. And then i create new emmc from newly build firmware 18.01,emmcfw can boot successfully. But semi, cfw, ofw all stuck at ns logo.
@@sthetixofficial step i already done today, rebuild nand using firmware 17 and 18,,recover using console backup which is v17. 0.1,reformat sdcard with latest hats pack, non of them work, still stuck nslogo in ofw/syscfw.
@@sthetixofficial hi today i try to remove pico rp2040 chip and install back emmc to the original position, suddenly the system can boot up normally, i follow the initialize setup and shutdown the system, afterthat, i reinstall back rp2040 picofly, its become normal back and boot up as usual. Thank you for the great video, learn alot from your channel
Fail at restore, it doesnt find the file. boot0 boot1 not find and same for emmc all... EDIT : my bad, it's ok 😬 thanks you for the tutorial, just perfect 👍
Hola Buenas Porque me da error en las particiones boot tengo diferencia de tamaños las que creo son de 1536KB y 512KB pero las que hago el backup son las dos de 4096kb
Bought a second hand OLED modded unbanned in firmware 17.0.1 booting ok in both emuMMC and sysMMC. I updated emuMMC, hekate and atmosphere using AIO updater. Followed a tutorial and matched the results. The emuMMC got updated correctly to 18.1.0, hekate to 6.2.1 and atmosphere to 1.7.1 with no errors. But, after that update I could not boot into sysMMC (semi stock). I can boot into emuMMC with no issues but not into stock firmware. The first Nintendo logo appears and then a very quick flash thin line on the screen and the screen went to black and didn't change from that. I had to reboot into hekate and then I could boot emuMMC. My burnt fuse info says (ODM 7/6): 19 | 0 - HOS: 17.0.0+ First, my hekate launcher didn't have another sysMMC besides the stock. I updated the ini file and then I got two sysMMC. The sysMMC (stock) didn't do anything but Nintendo logo and then black screen. The CFW sysMMC didn't do anything at all. I followed this tutorial after backing up my NAND. Now the CFW sysMMC (non stock) gives atmosphere logo and then black screen. The semi-stock OFW sysMMC gives Nintendo logo and then black screen. The emuMMC boots correctly. Some people say about faulty DAT0 but, as I said, before updating, the console booted ok into stock firmware. Really lost about what to do.
Hi, I can't backup nand because at 90% error reading 8192 block @ LBA 03488000 and when I try to access the system error code 2002-3580 which tutorial should I follow ?
I have a question. My switch is bricked and the PRODINFO, and USER partition is missing. But luckily i have prod.keys, and PRODINFO file backup from the past can i can restore my Switch with this method?
Hey! I followed all the steps but in the step to "Restore eMMC ALL", when I press POWER to continue, immediately "finished" the process with "Time taken: 0m 0s." but nothing shows in all (just the text of "Time taken", nothing more), it's a Hekate bug? Idk how I can solve it, please help :(( I thought the process would have already been done, but when I started SysMMC it show me the "pkg2 issue, Failed to boot HOS!"
@@sthetixofficial it's weird because i remove the .bin of all the "bcpkg2" and "boot0 and 1" files, and it's in the correct folder called "partitions" :( but with or without the missing files, the "restore emmc all" option doesn't work for me and only shows the "Time taken 0m 0s" EDIT: Idk what I did, but after bricking again my eMMC with that issue of "Time taken: 0m 0s", I decided to restore my nand backup (backup that I made several weeks ago) (BOOT0, BOOT1 and all the "rawnand" files), and when I decide to boot to SysMMC, magically boots with the Switch logo and nothing show any Atmosphere error or anything, just boot normally and immediately I turn off the Switch to boot Hekate, and when I boot Stock/OFW, it also boots too!! Again, Idk what happened in all, but I guess it is because my nand backup has the bcpkg2 partitions and seeing in GitHub and GBATemp forums, the reason why my switch was bricked is due the corrupted PRODINFO or saves (I highly doubt that you save them because when I deleted the ones that were recommended, when I boot OFW or SysMMC, just shows the Nintendo/Atmosphere logo and black screen forever, so my suspicions was the corrupted PRODINFO, and thanks to your tutorial, all the files with your donor nand and my prod.keys restores the corrupted PRODINFO, and only the latest issue was the bcpkg2 partition missing, but with my nand backup restored it without problems, and yeah, that's why my "variant" of your tutorial (and thanks!) (only in the case of the "Restore eMMC ALL" doesn't work for anyone, just use your nand backup as a complement for restoring the bcpkg2 partitions) :)
@@sthetixofficial yeah, probably is it, anyway I can unbrick my switch with the "extra step" i do (basically restoring my backup made to restore the missing bcpkg2 files, and the only corrupted file probably was my PRODINFO or saves), thanks for the tutorial! :DD
Literally came here as a last ditch effort trying to save my console but jo luck. After following all your steps I still get the same error on EmuMMC about error porgramm ID: 0100000000000016. I already checked the contents folder and that specific folder does not exist when I look for it. I'm starting to think that it may be a hardware problem
@@sthetixofficial no more pk91 thats works great but stil no luck for my the oled got stuck ad a firmware update its only see the nintendo logo than only black screen :(
@@sthetixofficial for xaw1000000 can access into switch but only cannot access eshop but when i put the original switch serial xaj4005 it's show error 20267-0002
@@sthetixofficialgood news my sysnand finally works again but now I’m trying to fix the Emunand pkg 2 decryption failed problem but I don’t want to erase everything on it because that’s what I use to play my switch is there a solution?
Hi sthetix, I was gaming on my Switch Lite + Picofly (RP2040) and then I had to re-do the soldering on the daughterboard connector because my left d-pad wasn't registering, which had me desolder RP2040 from the board. After the job was done, I resoldered everything but now my Lite will black screen when sd card is inserted & no backlight; but when card is removed, backlight comes on and the "no sd card" is displayed. Could that be a bad nand, did something get corrupted? I'm on the Lite, if those are the issues, will this video help me out?
Nxnandmanager keeps crashing when copying system files while being mounted. either it crashes like in your video or the transfer just slows down to 0kbps and sit there forever. any other tools/method that i can use to finish this transfer?
hi sthetix, I have an OLED console and a purple screen of death when loading the official firmware, but in Atmosphere on sysnand everything worked, I did everything according to the instructions and now it gives an error (ini1 parsing failed) when loading, I transferred everything several times the result is the same, firmware 18.1.0 downloaded 18.1.0-1.0 I also tried to install 18.1.0 without 1-0, the Nintendo logo appears and a black screen, tell me what it could be? or what did I do wrong?
@@sthetixofficial Same problem, ini1 parsing failed I redid everything several times, every time the same problem, I don’t understand what I’m doing wrong
for some dam reason its saying my prod keys dont match up with the prodinfo file, ive dumped them from the console time and time again and its always coming back as bad crypto
your prodinfo and your prod.keys should match. please check it by opening the prodinfo file using the nxnandnmanager along with your prod.keys obtained from the lockpick_rcm
@@sthetixofficial I've done that time and time again. I've even saved both the new dumps in a folder called new dumps to avoid confusing them for other dumps I've saved. It's bad crypto every time. The only thing I can thinnnkf is if someone has tried doing this before and messed it up?
@sthetixofficial Hi, I was wondering, out of curiosity, if I can use this method to create a clean nand for oled which can be compressed highly. I saw your Twitter post regarding the compression. I would like to be able to get a good ratio like that so it's small enough to store in the cloud. I have a full backup of sysnand already. I'm looking to replace it if it is safe. Hope you can clarify. Thanks in advance!
Too late for me, I guess. I used s demo games on my oled before factory resetting. then wiped it and sent it for a picofly install. They made a nand backup, but when I compress the nand it's only a bit smaller than 64gb.
Hey, It would be cool if someone made a video comparing the performance of the distros Ubuntu Bionic vs Ubuntu Noble vs Fedora 39 (L4S 5.1.2) running Gamecube, Wii or other real world benchmark test (without overclocking) to see the general optimization of the new available Linux for Switch.
Hello. After installing the modchip. Sysnand wont boot, and blackscreen after nintendo logo, after removing the modchip its still the same. Only emummc boots. V1 patched is my device. What version do you recommend to use. All emmc info is there and the user partition is there also.
Okay done on using this method and its show emmc is initialized in slower mode. I've read your issues with the picofly core modchip and its the same one that I've used. So my emmc is dead already? Should I swap it with new emmc and change the modchip? Or just the modchip?
I did a DIY thing but I have experience in microsoldering, so the emmc is now broken? Because after I remove the modchip its still the same it cannot boot in sysnand, should I replace the modchip and the emmc?
Hi there, my switch was originally hacked with sxos. I did something now it has hekate. But when I attempt to boot cow emunand or cow sysnand it gives me the message: "Unknown pk91 version. HOS version not supported!" but my OFW Launch does work. Can you advise on which guide I should follow to fix this and use my hacked switch.
@@sthetixofficial I removed the folder under /atmosphere/contents that matches another long number in my error message that ended in 7E51A and tried again. That worked. Found it on a Reddit thread.
Hi, first of all thank you very very very much, I finally been able to recover my Switch after update it to 17.0.0 and get a semi bricked Switch. Now I have a minor problem, when mi console went semi brick I made a SD content backup, but when I try to restore it to my fixed Switch it says that data is from another console and format the SD. Is there a way to recover those save games from before the "accident"?
no you cannot. it seems from another console but it is not. you need to know that if the console has been reset, it will ask you to delete the previous data
@@sthetixofficial HI, thanks for the response. I did this the last time I change the micro SD card a few days before my Switch bricked so I kept this backup in my computer to recover this data. There's any way to get this saves or I need to re play all those games
@@sthetixofficial Hi thank you for your responses & your time (and sorry for my english, its not my main language). I use two different cards for the OFW & CFW, when the update bricked my switch I copied the OFW content to my PC so in the future I could recover this saves. So I use the card in the console & formated it, then I copy the content from my PC to the card but when I use the card in my console it says that the data is from another console, but it is not is from the same Switch!! I don't know if I can patch those data or something like that, if not I'll loose a lot of game played (I know is not the end of the world, I'll replay those games)
If you have formatted the console then you cannot use your previous data. that's what the console do - FYI the formatting will generate a new unique "ID" so it cannot read the previous data
When you extract rar file donor nand file not wait too long time I dont know why it still to long time up %9 dowen 98% is this normal in all laptop or winrar. After that it finish like that now is The files that i have in donor is reall size... 😅
About fw hecgen it make file with out bin in the end is that wrong or normal.. The prod keys that have from console show the sirial is not same my console sirial is that wrong kyes from my console!!!
This literally saved my Switch, thank you so much for the detailed tutorial!
And Thanks again... my switch wouldnt go pass the nc logo in ofw and sysmmc mode... i rebuild my nand with this perfect video.. And everything is working again.. thnx for your hard work and this amazing video :)
You are welcome!
this new method is way more efficient than the old one. you are legend.
Boy,this is complicated. Good to keep in mind for emergencies
Perfect, was able to save a Switch with a purple screen.
always showing (Input file/drive is not a valid NX Storage) how do I fix this?
you need to rename the file to rawnand.bin
ive followed everything but still black screen after atmosphere logo. any idea? emummc works fine
EXCELENT MORE EFFICIENT THAN THE NORMAL VIDEO AND TOOO FAST!!! 3 SWITCH REVIVE FROM DEATH WITH THIS NEW METHOD
Hi! Thank you! With your tutorial I've fixed my console!
Great video. It worked for me to perform a test, my oled switch does not dump the nand nor create emunand, however I managed to separately dump all the partitions except "SYSTEM" and "USER", so with your method I created my Donor nand, and with this nand I created my "emunand", after several errors and attempts I managed to boot the emunand, however after some time the console crashes and it takes a long time to enter the emunand again. I probably have a physics error in my physical nand module.
in the minute 11:43 the nxnandmanager show this error (failed to mount filesystem) what should i do?
you need to install the dokan driver
19.0.0 Files Support. ¿Compatibility issues?
Still pre-release
You saved my NS v2 😊
My Switch oled live again!!! Thanks!!!
great tutorial as usual
THANKS
a question, what tutorial should I follow if I don't have any nand files, maybe I only have the PROD.KEYS, the nand is bad
you need to do the level3 guide .(this guide + the prodinfo_gen guide)
@@sthetixofficial thank you
@@sthetixofficialMay I know if you have a video for level 3? I cannot backup my nand as well… all missing….
@@sthetixofficialhello. Could y explain the order of actions? I should start from prodinfo guide and finish by level 2?
Yes, do the prodinfo_gen guide, and do the level 2 (the updated version)
good video thx bro have a nice day
Thanks bro!
You are welcome.
ohhh man is amazing this tutorial if jajajaja thank you very much ammm coming soon I donading :)
Any idea why NxNandManager crashes when trying to restore the encrypted SYSTEM partition?
Figured it out, needed a larger paging file size set in windows (virtual memory) even though I have 32gb of ram
When I select the pro, keys and firmware, an error pops up Version NCA(pid010000 And so on) was not found
you opened the nand?
@ I solved this problem simply by formatting the memory card to a different format.
Please post a video about BAN removal. I get excited when I get a notification from you channel saying there will be a video about this.
Not possible, Nintendo had really beefed up security since the 3ds.
@@rohansharma8956 do you think using this metod i can fix the start up messenger can't run this software ?
@@braianmanueljoaquinleonor9380 u can fix that by reinstalling the game and updating the sigpatches (latest HATS pack has them). U don’t need to reinstall the nand for that
same error at end could not start the software hahaha
there is no method available to remove the ban from the nintendo switch, advice for life: next time be more careful and set up all the necessary defenses to avoid the ban
Excellent video! Thanks, one more switch saved from brick.
Any idea why Console Serial number is XAW1000000000? after unbrick? I boot to ofw with no SD inside (unpatched).
do you have the original prodinfo from the console?
@@sthetixofficial I am not sure. The console's SD was a mess with a prodinfo files and a generated prodinfo file. It's not mine.
then you dont have any other option.
can i use this method if i don have the original prod.keys backup ?
After completing the procedure without errors, when I start CFW SysNand I see the Atmosphere logo and then the screen remains black.
If I try to start OFW instead, I see the Nintendo logo and then the screen remains black.
The crazy thing is that if I try to create the emuMMC and start it the emuMMC works perfectly
it depends on the chip you are using.
@@sthetixofficialRP2040 Zero
Hi, I have a problem with a friend's Switch, he used SYSNAND all this time, even though he had EMUMMC installed, his SYSNAND got corrupted and he can no longer use OFW, but the EMUMMC boots normally and can be used.
Can I make a copy of the EMUMMC and transfer it to the EMMC? Please help me, I am using a translator to write this
You can!.
Can you copy tour emuMMC to your sysMMC and not be banned? I can not pass Nintendo logo in my OFW nor in my sysMMC but can boot ok into emuMMC.
is fat32 sd card supported? i'm still getting a black screen when launching ofw and cfw
it does. maybe you did not do the guide properly
Hello, friend, thank you very much for making your time and experience available on the subject... I have an OLED that when I insert a game card or connect it to the internet gives error 2123-0011, but only on the ORIGINAL system, would there be a solution?
The unlocking system works normally.
what is the error message?>
@@sthetixofficial In the original system, after a few seconds with the game card or when I connect to the internet via Wi-Fi, I get the error 2123-0011.
The following message:
Error code: 2123-0011
Press the POWER button and restart the console [...]
(X1) XAW1000000000
(X2) 18.1.0
hey. i have a question, after restoring BCPKG files, pops up EMMC is initialized in slower mode , well i hit ok and then follow your guide, when i hit launch, atmosphere launches, and stays black screen without nintendo logo without anything, do you know anything about this? some help ?
your emmc is f#cked , either it is really fcked or the modchip is causing this (if you use pico)
my own switch prodinfo is bad crypto, cannot encryt. how do i do from here
where is the original prodinfo?
Does this fix empty partition table? I have all the keys from donor that I had fixed a few days ago but I accidently removed the rawnanad on Hekate and only left with the other files
if you have a backup nand, just flash it to your console.
I had problems with crashes. V1 model unpatched. Error code 2162-0002 (0x4a2). I couldn't find any solution so I decided to try to unbrick it. I did the level 1 with no success. Then i tried the level 2. Now things are even worse. When I choose to install the sysMMC or the stock ofw switch won't boot up and stays in black screen without even show atmosphere or switch logo. I don't know if it matters but I used the latest firmware 18.1.0 but in hekate in console information it says 17.0.0.
You need to know not all BRICKS come from the NAND. It could be your console's power chips are failing etc.
when trying to encrypt and dump the console prodinfo to the encrypted folder its saying bad crypto and im unable to dump it, what have i done wrong?
please re-watch the guide.
need some help here:
got a oled and a v2 bugging out not booting ofw/sysnand (stuck at switch logo or giving 2002-3540 error), emunand boots without problem
*the oled i'm having this problem since last week and haven't been able to fix it without removing the chip (removing the chip makes the console boot without problems, already changed the chip and the flats/wires 3 times so i dont believe they are the issue), if i restore a donor nand or the emummc to the emmc it gives a emmc error(slower mode) after is done and corrupts (purple/blue screen)
*the v2 i just installed the chip a few moments ago and it bugged after creating the emunand (used a nxcore so is not a solder joint problem as it just has the soldering on the nvidia chip)
*restoring only the boot0/boot1 to the emmc on the v2 and on the oled seems to "wipe" the emmc contents (emmc in slower mode and partition table is empty)
forgot to add, both consoles bugged out after the 19.0.0 update
how did you brick your sysmmc
@@sthetixofficial its not bricked, if i either disconnect the flat from the chip or just the dat0 wire, the console boots normally
also, already fixed the v2, just had to swap the chip until one worked
so you have fixed it?
Hi sir i need your help please, i have v2 with firmware 17.01 using hats pack, everything is fine until i boot into ofw to factory reset and online update firmware, but both give me an error and was not successful, then my switch cannot boot into ofw anymore. Today i follow this video to rebuild sysnand to v18. 01 using my backup keys. And then i create new emmc from newly build firmware 18.01,emmcfw can boot successfully.
But semi, cfw, ofw all stuck at ns logo.
check your fuse count please.
@@sthetixofficial fuse count 19,HOS 17.0.0+
I think 18 firmware should work?
@@sthetixofficial step i already done today, rebuild nand using firmware 17 and 18,,recover using console backup which is v17. 0.1,reformat sdcard with latest hats pack, non of them work, still stuck nslogo in ofw/syscfw.
well, maybe the emmc chip is damaged or something else.
@@sthetixofficial hi today i try to remove pico rp2040 chip and install back emmc to the original position, suddenly the system can boot up normally, i follow the initialize setup and shutdown the system, afterthat, i reinstall back rp2040 picofly, its become normal back and boot up as usual.
Thank you for the great video, learn alot from your channel
Fail at restore, it doesnt find the file. boot0 boot1 not find and same for emmc all...
EDIT : my bad, it's ok 😬 thanks you for the tutorial, just perfect 👍
what did you do? i got the same problem
Hola Buenas Porque me da error en las particiones boot tengo diferencia de tamaños las que creo son de 1536KB y 512KB pero las que hago el backup son las dos de 4096kb
It doesnt matter.
@@sthetixofficial si me ha funcionado perfecto muchas gracias por su video excelente
Bought a second hand OLED modded unbanned in firmware 17.0.1 booting ok in both emuMMC and sysMMC. I updated emuMMC, hekate and atmosphere using AIO updater. Followed a tutorial and matched the results. The emuMMC got updated correctly to 18.1.0, hekate to 6.2.1 and atmosphere to 1.7.1 with no errors.
But, after that update I could not boot into sysMMC (semi stock). I can boot into emuMMC with no issues but not into stock firmware. The first Nintendo logo appears and then a very quick flash thin line on the screen and the screen went to black and didn't change from that. I had to reboot into hekate and then I could boot emuMMC.
My burnt fuse info says (ODM 7/6): 19 | 0 - HOS: 17.0.0+
First, my hekate launcher didn't have another sysMMC besides the stock. I updated the ini file and then I got two sysMMC. The sysMMC (stock) didn't do anything but Nintendo logo and then black screen. The CFW sysMMC didn't do anything at all.
I followed this tutorial after backing up my NAND. Now the CFW sysMMC (non stock) gives atmosphere logo and then black screen. The semi-stock OFW sysMMC gives Nintendo logo and then black screen. The emuMMC boots correctly. Some people say about faulty DAT0 but, as I said, before updating, the console booted ok into stock firmware.
Really lost about what to do.
It has nothing to do with the DAT0.
so your sysmmc is damaged but emummc works fine?
@@sthetixofficial yes. I can boot emuMMC with no trouble. Only semi stock sysMMC and atmosphere sysMMC don't boot.
you can dump or backup the emummc then later flash it to your sysmmc
@@sthetixofficial Thanks for replying! Is that procedure a Nintendo ban low risk? I presume, right?
after restoring the emummc, do the systemwipe.
Currently my Switch is at 17.0.0, do I have to use the 18.0.0 FW for this to work? I can't use a lower firmware?
use the latest fw, but if you are free to choose 17.0.0
Hi, I can't backup nand because at 90% error reading 8192 block @ LBA 03488000 and when I try to access the system error code 2002-3580
which tutorial should I follow ?
i think your emmc chip is damaged, or maybe your SD card is damaged, please try to replace the SD card and backup the nand again.
@@sthetixofficial I already tried to use a different SD card, but i have the same error, what else should I try? ?
I have a question. My switch is bricked and the PRODINFO, and USER partition is missing. But luckily i have prod.keys, and PRODINFO file backup from the past can i can restore my Switch with this method?
you can follow this guide to make a new nand
Hey! I followed all the steps but in the step to "Restore eMMC ALL", when I press POWER to continue, immediately "finished" the process with "Time taken: 0m 0s." but nothing shows in all (just the text of "Time taken", nothing more), it's a Hekate bug? Idk how I can solve it, please help :((
I thought the process would have already been done, but when I started SysMMC it show me the "pkg2 issue, Failed to boot HOS!"
you did not put the files inside the correct folder. please check again and maybe you did not remove the file extension.
@@sthetixofficial it's weird because i remove the .bin of all the "bcpkg2" and "boot0 and 1" files, and it's in the correct folder called "partitions" :(
but with or without the missing files, the "restore emmc all" option doesn't work for me and only shows the "Time taken 0m 0s"
EDIT: Idk what I did, but after bricking again my eMMC with that issue of "Time taken: 0m 0s", I decided to restore my nand backup (backup that I made several weeks ago) (BOOT0, BOOT1 and all the "rawnand" files), and when I decide to boot to SysMMC, magically boots with the Switch logo and nothing show any Atmosphere error or anything, just boot normally and immediately I turn off the Switch to boot Hekate, and when I boot Stock/OFW, it also boots too!! Again, Idk what happened in all, but I guess it is because my nand backup has the bcpkg2 partitions and seeing in GitHub and GBATemp forums, the reason why my switch was bricked is due the corrupted PRODINFO or saves (I highly doubt that you save them because when I deleted the ones that were recommended, when I boot OFW or SysMMC, just shows the Nintendo/Atmosphere logo and black screen forever, so my suspicions was the corrupted PRODINFO, and thanks to your tutorial, all the files with your donor nand and my prod.keys restores the corrupted PRODINFO, and only the latest issue was the bcpkg2 partition missing, but with my nand backup restored it without problems, and yeah, that's why my "variant" of your tutorial (and thanks!) (only in the case of the "Restore eMMC ALL" doesn't work for anyone, just use your nand backup as a complement for restoring the bcpkg2 partitions)
:)
@AlonCV all switch consoles have the bcpkg2 files. I guess your alphanumeric folder is not correct or doesn't match so hekate couldn't pick them up
@@sthetixofficial yeah, probably is it, anyway I can unbrick my switch with the "extra step" i do (basically restoring my backup made to restore the missing bcpkg2 files, and the only corrupted file probably was my PRODINFO or saves), thanks for the tutorial! :DD
Literally came here as a last ditch effort trying to save my console but jo luck. After following all your steps I still get the same error on EmuMMC about error porgramm ID: 0100000000000016. I already checked the contents folder and that specific folder does not exist when I look for it. I'm starting to think that it may be a hardware problem
can you boot the OFW?
@sthetixofficial I am unable to boot into OFW
i got a error unknown pk91 version (failed to launch hos)
Try using the latest hats www.sthetix.info/hats/releases
@@sthetixofficial no more pk91 thats works great but stil no luck for my the oled got stuck ad a firmware update its only see the nintendo logo than only black screen :(
Hi! Will be new method 3 guide?
yes it is similar to the level2 but with additional prodinfo_gen procedure
hi,can i check. i received error code 2026-0002. what do i need to do
Sorry I dont know about it.
@@sthetixofficial for xaw1000000 can access into switch but only cannot access eshop but when i put the original switch serial xaj4005 it's show error 20267-0002
@@sthetixofficial i got error 20267-0002 on actually xaj40053 serial while on inconito mode xaw10000 can access
@@sthetixofficialI get error 2026-0002 on actual console serial xjaw4000 but when console serial xjaw1000 incognito mode can access
I got a question I mainly want to fix the Emunand part of the switch is the process the same as sysnand
yes it is the same but using the level2, it will wipe everything, so try using the level 1 guide first
@@sthetixofficialgood news my sysnand finally works again but now I’m trying to fix the Emunand pkg 2 decryption failed problem but I don’t want to erase everything on it because that’s what I use to play my switch is there a solution?
try doing the level1 unbrick , the newest method.
Thank You, this fixes the OLED switch with stuck logo issue after modchip installation
Is it is safe to connect the sysnand to the online server?
yes if you dont have pirated games on it.
Hi sthetix, I was gaming on my Switch Lite + Picofly (RP2040) and then I had to re-do the soldering on the daughterboard connector because my left d-pad wasn't registering, which had me desolder RP2040 from the board. After the job was done, I resoldered everything but now my Lite will black screen when sd card is inserted & no backlight; but when card is removed, backlight comes on and the "no sd card" is displayed.
Could that be a bad nand, did something get corrupted? I'm on the Lite, if those are the issues, will this video help me out?
it could be anything, because as far as I know, the pico could kill your console
@sthetixofficial is there an affordable alternative that you could recommend, please?
Instinct-nx
Whar can I do if my switch show com 3 error when I use emmc raw gpp
I cant seem to use emmc raw gpp on a long time any substitution on this
Nxnandmanager keeps crashing when copying system files while being mounted. either it crashes like in your video or the transfer just slows down to 0kbps and sit there forever. any other tools/method that i can use to finish this transfer?
shorten the USB cable, change your USB port. Or use the older level 2 unbrick guide.
Try running as administrator
hi sthetix, I have an OLED console and a purple screen of death when loading the official firmware, but in Atmosphere on sysnand everything worked, I did everything according to the instructions and now it gives an error (ini1 parsing failed) when loading, I transferred everything several times the result is the same, firmware 18.1.0 downloaded 18.1.0-1.0
I also tried to install 18.1.0 without 1-0, the Nintendo logo appears and a black screen, tell me what it could be? or what did I do wrong?
try to repair it with the guide or at least the level1 guide
@@sthetixofficial Same problem, ini1 parsing failed
I redid everything several times, every time the same problem, I don’t understand what I’m doing wrong
i dont know about parsing, where did you read it.
@@sthetixofficial This message appears when boot up ofw
Does such a method also exists for (New) 3DS console?
the ntrboothax
@@sthetixofficial Thanks for answering!
@@sthetixofficialWould you mind quoting the video you are referring to? 🙏
You can search the ntrboothax on my yt channel.
@@sthetixofficial Will do. Thank you so much, your work is highly appreciated!
for some dam reason its saying my prod keys dont match up with the prodinfo file, ive dumped them from the console time and time again and its always coming back as bad crypto
your prodinfo and your prod.keys should match. please check it by opening the prodinfo file using the nxnandnmanager along with your prod.keys obtained from the lockpick_rcm
@@sthetixofficial I've done that time and time again. I've even saved both the new dumps in a folder called new dumps to avoid confusing them for other dumps I've saved. It's bad crypto every time. The only thing I can thinnnkf is if someone has tried doing this before and messed it up?
@sthetixofficial Hi, I was wondering, out of curiosity, if I can use this method to create a clean nand for oled which can be compressed highly. I saw your Twitter post regarding the compression. I would like to be able to get a good ratio like that so it's small enough to store in the cloud. I have a full backup of sysnand already. I'm looking to replace it if it is safe.
Hope you can clarify. Thanks in advance!
no you cannot. the only way to get a 650MB compressed NAND is to dump it after you mod it.
You mean to mod before actually using it at all and then wiping before modchip install?
@genkidoesgaming no, update the console to the latest, no need to link the user profile to nintendo. then mod it and dump using hekate.
Too late for me, I guess. I used s
demo games on my oled before factory resetting. then wiped it and sent it for a picofly install. They made a nand backup, but when I compress the nand it's only a bit smaller than 64gb.
@genkidoesgaming you can try it later with a new console.
Hey, It would be cool if someone made a video comparing the performance of the distros Ubuntu Bionic vs Ubuntu Noble vs Fedora 39 (L4S 5.1.2) running Gamecube, Wii or other real world benchmark test (without overclocking) to see the general optimization of the new available Linux for Switch.
If you keep getting the error towards the end where you mount and copy the files, run the NX took as administrator
hi, I should solve the problem "failed to match warm boot with fuses"....can you help me? Thanks.
that's not the solution. The solution for your case is to update your console to the latest firmware (on both sides - the sysmmc and emummc)
@@sthetixofficial Ok, do you have a simple guide to recommend?
yes please watch my daybreak guide (offline update)
@@sthetixofficialunfortunately I can't start daybreak, atmosphere doesn't start, that error message always appears.
You should IGNORE that message by pressing the Power button. It should boot to Atmosphere.
Hello. After installing the modchip. Sysnand wont boot, and blackscreen after nintendo logo, after removing the modchip its still the same. Only emummc boots. V1 patched is my device. What version do you recommend to use. All emmc info is there and the user partition is there also.
Okay done on using this method and its show emmc is initialized in slower mode. I've read your issues with the picofly core modchip and its the same one that I've used. So my emmc is dead already? Should I swap it with new emmc and change the modchip? Or just the modchip?
you should not be using the pico. please use the instinct-nx or hwfly
I did a DIY thing but I have experience in microsoldering, so the emmc is now broken? Because after I remove the modchip its still the same it cannot boot in sysnand, should I replace the modchip and the emmc?
Yes, replace the modchip, and try to unbrick it using my level 1 or level 2 guide.
@@sthetixofficial but what a problem with pico?
Hi there, my switch was originally hacked with sxos. I did something now it has hekate. But when I attempt to boot cow emunand or cow sysnand it gives me the message: "Unknown pk91 version. HOS version not supported!" but my OFW Launch does work. Can you advise on which guide I should follow to fix this and use my hacked switch.
try re extracting my hats pack, t.me/HATSPACK
@@sthetixofficial it gives a different kind of error now. I click Sysmmc cfw but after the switch logo it says error code 2168-0001 (0x2a8)
if ofw launch normally, the sysmmc should be able to work too. delete everything inside the sdcard and try to re extract the pack
@@sthetixofficial
I removed the folder under /atmosphere/contents that matches another long number in my error message that ended in 7E51A and tried again. That worked. Found it on a Reddit thread.
I cant seem to be able to get your new HATS pack,I did successfully do this a couple yrs ago.
u.pcloud.link/publink/show?code=XZgNEz0Z5q4A5xx3CtyQf3hwI3Jij8M5DcOk
Thank you.
Hi, first of all thank you very very very much, I finally been able to recover my Switch after update it to 17.0.0 and get a semi bricked Switch. Now I have a minor problem, when mi console went semi brick I made a SD content backup, but when I try to restore it to my fixed Switch it says that data is from another console and format the SD. Is there a way to recover those save games from before the "accident"?
no you cannot. it seems from another console but it is not. you need to know that if the console has been reset, it will ask you to delete the previous data
@@sthetixofficial HI, thanks for the response. I did this the last time I change the micro SD card a few days before my Switch bricked so I kept this backup in my computer to recover this data. There's any way to get this saves or I need to re play all those games
you cannot, unless you have extracted the save data earlier
@@sthetixofficial Hi thank you for your responses & your time (and sorry for my english, its not my main language). I use two different cards for the OFW & CFW, when the update bricked my switch I copied the OFW content to my PC so in the future I could recover this saves. So I use the card in the console & formated it, then I copy the content from my PC to the card but when I use the card in my console it says that the data is from another console, but it is not is from the same Switch!! I don't know if I can patch those data or something like that, if not I'll loose a lot of game played (I know is not the end of the world, I'll replay those games)
If you have formatted the console then you cannot use your previous data. that's what the console do - FYI the formatting will generate a new unique "ID" so it cannot read the previous data
Can this method keep the online from stock firmware? (I'm not banned and I have my ProdInfo)
you can as long as your console is not banned previously
Boa noite, tenho switch oled eli ligar aparece o logo nintendo e depois disso ficar tela preta
saved my console tysm
When you extract rar file donor nand file not wait too long time I dont know why it still to long time up %9 dowen 98% is this normal in all laptop or winrar. After that it finish like that now is The files that i have in donor is reall size... 😅
it takes a long time to extract the donor
About fw hecgen it make file with out bin in the end is that wrong or normal..
The prod keys that have from console show the sirial is not same my console sirial is that wrong kyes from my console!!!
Thank you but where I can find the donor nand link please ?
I've added the link. thx
@@sthetixofficial thank you so much ☺️
I still have a yellow screen at the end plz help )))):
yellow means your wifi chip could be damaged, try running android and test it.
@@sthetixofficial wdym run android? I dont have Android on my switch
you need to run android on your switch to test the wifi. install lineage or ubuntu on your console to find it out.
Yeeeeeeeeeeeeeeees!!!!
+ rep HOLY THANK YOU
Falta un archivo de la donor nand de 32 gb
what file?
bad crypto no me deja vanzar
falta el donor_prod.keys
you can ignore the donor_prod.keys as the script now using the donor.keys