FYI, you need to put the donor_rawnand.bin in the same directory/ location / folder as the NANDFIX app, so it will be able to build a complete rawnand.bin either 32GB or 64GB.
I have a problem. switch OLED Atmosphere Right Joy not connect. But Joy copy is Connect. Has anyone encountered this problem? And how to fix it? Thank you
I hope i want need it but when i know where to look up the solution. BTW really greatfull for your guides. Helped me a lot in the beginning. The Switch lite and oled works like a charm :)
Good job buddy! also people should know that this should perform faster than previous methods as user decrypt and encrypt are minimized in size, it also decreases the free space requirements by a factor 2. Excellent! 👌👍
for decrypt, i limit the user to 250MB only. and later of course you need to contain the rawnand that is 32GB or 64GB, so you need a large harddrive. FYI encrypt took the same size, so yes 250MB. so yes, by using the nandfix, it wont take much space.
@@sthetixofficial thanks for the clarification! Not only you made it take less space, you also made the procedure faster. This is clear now and it's even better! :) great work buddy!
logre reparar la nand de la switch v2 averiada. compre una memoria sd nueva y una emmc por aliexpress. segui el tutorial exactamente paso por paso excepto por una cosa, primero formatee la sd en exfat y luego introduje la ultima version athmosphere, seguidamente segui todo el tutorial y consegui arrancar la swich en modo HOS. muchas gracias por todas las herramientas. I managed to repair the faulty NAND on my Switch v2. I bought a new SD card and an EMMC card from Aliexpress. I followed the tutorial exactly step by step except for one thing, first I formatted the SD card in exfat and then I inserted the latest version of Athmosphere, then I followed the entire tutorial and managed to boot the Switch in HOS mode. Thank you very much for all the tools.
My switch is on the technician after I try update. He call me saying is bricked can't found nand. He will work on it all night and call me tomorrow. I hope he know about this method
thx for the app. it saves time by no having to click "yes" a bunch of times. would be nice if you could merge the, generate, decrypt,encrypt and build button into a single button so one can leave the pc and do something else while the new nand is beeing build.
Hello, like always your videos are the best, good explanation and quality. However, I have a question, I have a backup of my old Switch and want to restore that Nand into a switch that I replace de Nand chip (its blank) want to do it with that not with the donor Nand. on the donor Nand can't play locally monster hunter.
Hi sthetix. Great video! I'm having this issue with eMMC partition table empty and I don't have a sysNAND backup. However, I found a PRODINFO file backup from the atmosphere folder, but it only has 32kb. This PRODINFO file can be used with you unbrick method? In that case, I would recreate a NAND from donor and use this PRODINFO from the atmosphere folder? Another question, my emuMMC is still working just fine. Can I restore my sysNAND with the emuNAND .bin files? Or the PRODINFO from emuMMC can't be used?
This could Work for a Switch 1.1 With error 2153-0321?, the error appeared after updating the console in OFW mode, and now the console is stuck in 2153-0321 screen always in OFW, however in CFW boots fine.
This was a great video. I'm going to try this on a switch lite that I attempted a mod chip install on. I didn't knock any components off and I think it did something that corrupted the nand. I get a similar color screen when trying to boot the console.
16:54 Wait, so if I follow this guide will I lose internet access on ofw? (for the record, I have a system backup but your restore level 1 & 2 haven't worked for me so now I'm on level 3. Can I get my legit prod key from my backup? If not can't I use a donor prod key and have internet access?)
If you already have a nand backup previously, DO NOT do this guide as you will lose access to the nintendo server, unless you have the original PRODINFO from the console. Prod.keys and PRODINFO are two different thing.
@sthetixofficial I found my legit prodinfo data and am currently still following this guide, is that ok? Will my internet access be ok? (I'm past the building stage. It says 'failed to locate driver files'when attempting to mount rawnand.bin on NXmanager. What should I do? I'll hang to your word for the switch's sake. Thanks!)
@@sthetixofficial I actually found my og prodinfo and created the build, but when I connect the emmc raw gpp to my pc, it can't be recognized and won't work on Rufus. What do I do?
I couldn't manage to repair it. Could it be that it doesn't work in version 19.0.1? I repaired 3 consoles a long time ago, but with the previous video, could it be that it doesn't work in the new version? I carry out all the processes and I can even restore the boot0 and boot1 files but when I want to start it does not turn on. I hope you can help me, thanks in advance
hi, thank for your videos, i has made some of then before, this time im following the guide carefully, and i cant boot the console, im getting black screen. i can use this new generated rawnand to flash my console from scratch with the older level 3 method? or how i can do it? btw, i have an 2019 mod chipped console...
@@sthetixofficial hi, thanks for your response, my problem is i has been formatted the console's nand, i deleted all in there, in this case may i follow this guide and let the rufus complete all the copy? or how i can fix it?
I'm trying to follow the tutorial but at minute 4:41 it won't let me use the option (build prodinfo file from donor) why could this happen and how can I solve it? thank you so much
@@sthetixofficial I don't know how to figure that out, I only got to that part of the video and I couldn't continue because the (build prodinfo) appears in black and doesn't let me choose it, do you have any idea what I might be doing wrong? thank you so much
Hello - fingers crossed for this one. Running into an issue - when I run "prodinfo_gen" "Build PRODINFO file from donor" remains greyed out. Any ideas?
My console has never been banned before following your guide, after repairing the nand can I safely connect my switch to the internet or will I immediately be banned?
So this only works in cfw? What happens if you try and connect to online services in cfw now the sysnand is clean? Does it just say "restricted". I assume so? And I'm assuming you can't just get an unbanned serial to use with prodigy? Would that risk the other console getting banned?
I already resurrected a V1 with dead NAND using your old guide, after getting a new NAND module from Aliexpress. Is there any advantage in following this new method again?
@@sthetixofficial for a new console to resurrect that's for sure, but what about a console already resurrected with the old method? Any advantage to use this new procedure again?
@@sthetixofficial that's what I thought too but two machines in a row now.. USB picks up perfectly fine In Hekate and I'm able to browse the SD card and the emmc raw gpp but when it goes into cfw it stops detecting usb. Will just charge.. if you can test a system and let me know that would be great
@@sthetixofficial The emunand is not yet set up and the emmc seems to be broken. It would be great if i could bring the Switch back to life with an emunand, even with a defective emmc.
Gracias Men. ya ocupaba una guía así. tengo un par de dudas espero algún Dia las puedas responder. 1. Si mi Switch le instale Magia, y al iniciar el ofw se queda en el segundo logo de Nintendo switch. ocuparía hacer esto oh con reinstalar el firmware con sus prod keys. se solucionaría* 2. Digamos que hago lo anterior de dumpear las keys y prod que trae la consola. Restauro la nand donante y uso las keys y prods originales*. conservo el online o al terminar el proceso la consola quedaría en pantalla negra o iniciaría normal*
Is it important to which firmware i choose for this method? My previous nand compeletly destroyed and i have no access to firmware .so i replaced nand chip with new one . With all firmware on this method i get black screen on ofw & cfw.
Same thing here. I followed all the steps and everything went through without errors but still black screen on ofw and cfw. Android and linux run fine. Did you manage to figure out what the issue is?
My picofly switch is no sd without sd, blackscreen with sd and bsod when + and - together with power button. How can I launch into hekate? is there somethiing wrong with my installation?
today when I restarted the cursor to hekate, there was a troll face instead of the cursor and the steering was reversed. maybe you know how to fix it. I don't know what could be the cause of this because I didn't install anything. 😭pls help😭
Hey, thanks for nice and clear video, mine is bricked cant enter into any sys(oled modded), but when i tried backup it came to 97% and aborted. In one video you said any backup is good, so im not sure which level/video to follow for unbrick, any recommendations?
as long as you have the prodinfo intact you can follow the level1. or level2.. you can use this video guide too but substitute the prodinfo with your console's prodinfo
Thank you for your work 💪 I have an Oled which has a freeze problem. After launching a game, the switch freeze after the loading screen or after 2-5min of playing. With cartridge or backup, same. Some big game run just fine so I think about sysnand and restore it, level 2, same. Reball emmc, checking short, everything is ok. Maybe you have an idea ? Thanks you boss 💪
i have a mariko switch with (probably) defective emmc. The switch does not boot at all, and I also have a missing 1.3V rail. I have an empty nand and would now like to implement this guide. But if I see correctly, I have to install a picofly to get into the hekate at all, right?
Interesting tutorial thanks, I'm using a windows arm version (because of running it under vmware on macbook m3) and I'm stuck at the "Encrypt" step of NANDFIX ! Unfortunately it's not doing anything and I have no logs of what it is supposed to do, so I can't find what is going wrong. I tried to check NANDFIX source code to see but it's not available :( Could you tell what command is ran by the encrypt button ? Edit : it seems it is using the NxNandManager encrypt feature, I'll try to do this step manually to progress ... Edit 2 : The dokan driver to mount partition doesn't seems to work on arm64 windows :( I'll find a x86 windows then ...
@@sthetixofficial I've just tried using a x64 windows 11, and I still have the same problem at the encrypt step with NANDFIX, it says encryption ok but not a single .enc file is created. Runing NxNandManager GUI is working well so I'm not missing any library to make it run ... I used NxNandManager gui to encrypt different files and I'll continue the process to see if it works ...
I use windows 11, x64, and encrypt worked fine. if it doesnt, then you need to check the prod.keys and the donor.keys file re-extract the donor rawnand and its donor.keys
I'd argue that the sysmmc isn't useless in this case. You're already SOL when it comes to connecting to Nintendo servers, so might as well use it to save some games to if you're out of space on your SD card lol
I gave it a try, but it keep showing me the message --mariko returned non-zero exit status after pressing generate but. I would really appreciate any suggestion on this trouble, its my first try on nand problem XD
@sthetixofficial yeah, seems like my atom based laptop doesn't work fine with Microsoft services. I tried on different PC, and succeed with it. Thank you very much on simple and clear instruction!
The nandfix software gives a non-zero exit status regarding the firmware, with the argument -mariko autorcm. Any way I can fix this? I have retried the lockpick rcm script several times, yet the error in nandfix always reccurs. What do I do?
@@sthetixofficial Now when the nands are fully combined the firmware version cannot be found. Before combining, specifically the system partition, the firmware version was shown as 12.0.2 (wrong one, as I use 15.1.0), but after it shows FW not found. Everything else seems fine, like the serial number created via prodify. When the boot0 and boot1 are loaded onto the switch, the size of the SD card backup does not match eMMC's selected part size. If I continue, the Nintendo logo flashes then turns black if booted into OFW, and the processor gets hot. I have repeated the process with several firmware versions, and only the 15.1.0 has resulted in this, others made blue screens. Any way I can fix this?
@@sthetixofficial As I have previously stated, any other firmware results in a blue screen. The 15.1.0 is the only version that even gets a Nintendo screen. I believe that the prodinfo is the culprit, as it is responsible for displaying the firmware version, though I don't know for sure. Is it time to give up?
Dont know why, but if you use a higher firmware like 18.0.1 and the console has an old firmware installed, you get an error on the Generate button. my faulty emmc console was on fw 17.x.x with burned fuses to these firmware. maybe the generated keyfiles dont match with the files of higher firmwares in these case?! Only Guessing!
@@sthetixofficial from your Page. The latent 18. In the list. Process is working atm. Only nxnandmanager seid unknown firmware after Import the emmc files.
@@sthetixofficial Strange, i already answered yesterday. Got the firmware from you page. the latest 18.0.1. / Used now the 17.0.0 and works fine. Good solution and easier as the last nsw 3 ;) The old serial number in the system is great ;)
I have a problem. switch OLED Atmosphere Right Joy not connect. But Joy copy is Connect. Has anyone encountered this problem? And how to fix it? Thank you
Hi there Man, afterusing the level 2 and not suceeding, now I am trying the level 3 with my original prodinfo. But the Nandfix pop out an error saying that "The loaded prodinfo is encrypted, cannot proceed". Is there any other way to goo around this ?
@@sthetixofficial Thanks man, after following your guide, it can be done. The only problem left is my switch only show the Nintendo logo and proceed with blank screen. On that note, after restoring the EMMC boot0 and boot 1, there is a prompt that pop out saying that EMMC in slow mode. Is it possible that my NAND Chip is broken?
I followed the steps to the letter, then when I reboot>ofw the Nintendo logo comes out and then it stays on the black screen. The switch worked fine, I had it installed the chip and now only the CFW mode works, any idea to make the OFW work?
@@sthetixofficial Currently in the emummc system I have the 19.0.0 with atmosphere, and I followed your video with firmware 19.0.1 and it still doesn't work, nintendo logo appears and then black screen, I made an emummc of my current nand and run it in CFW and it works, it starts as if I was just bought the console, so I guess it worked as such, only when running sysnand it does not boot, only with CFW
@@sthetixofficial Mine is the Oled, I follow the video exactly as you do, but when I try to enter OFW it takes 15 minutes for the Nintendo logo to appear and then another 15 to 20 minutes to start the system, then with the system working if it enters stadby it freezes, having to turn it off and on again.
@@sthetixofficial I managed to solve the problem, I noticed that there were some markings on the Switch board, I believe that this console was remanufactured, so I did reballing e o Switch voltou ao normal. So I put back the original Nand backup and it went back to normal, in fact after the reballing it was already normal, but I wanted to go back to the original prodinfo
I tried the tutorial 3 times. After the nand fix build task, nxnandmanager says ( fw ver: Not found). Note that I skipped the the prodify steps because you said it is just aesthetical. Any help?
FW file not found doesnt mean the nxnandmanager is faulty, but maybe you did not download the nxnandmanager that can detect 18.1.0 firmware or later. try this www.mediafire.com/file_premium/x4unhcftn8er945/NxNandManager_v5.2_x64_18.1.0.zip/file
it should always can detect the FW version, but that is not important, the thing is if the app succesfully generated the 32GB or 64GB rawnand.bin then you can flash it to your console.
I downloaded the nxmanager in the link and now it is showing the correct fw version. But I ended up with a black screen and modchip not glitching anymore until I disconnect the battery. I even deleted the .bin extension on the bckpkg , still black screen. Maybe hardware issues, I dont know what to try next
hi, i have problem when mod v2 using picofly 2002-3540 on the brand new v2 synthomp : using daybreak for update the ofw, and failed cannot 100%, after this, ofw and sysnand many times will show 2002-3540, sometimes can boot normally im technician on mod switch, thanks
Hello Sthetix .. Please could you help me, my console is a demo console that is in stores. the format and I got this message (Could not start the software). Can you revive my console.. Thank you..
@sthetixofficial I have done both. I don't even get an error when booting into atmosphere it just shows the logo and then black. And I think atmosphere gives you an error saying you installed the wrong console type if im not wrong but in my case it just goes black.
@@sthetixofficial i like you time to dedicate make this tutorials ... i been try 3 level of this but i cant run the nintendo .... just only can boot in hekate. i have v1 unpatched consolte whit full wiped sysnand
in the other side its normally when i go flash whit rufus v1 unpatched rawnand.bin says in the partition scheme GPT ? target system uefi ( non CSM ) , Cluster Size 16 Kilobytes and File System Fat32 i said this for in the video in minute 14:48 its like different
if you did this guide. then you won't be able to link your nintendo account legitly. unless you use the original prodinfo and your console is not banned yet
I recently updated ofw to 19.0.1 along with hekate update to 6.2.2 and ofw works normally after the update but blue screen appears on the current stock. I didn't update the atmosphere to 1.8 because I'm not sure if the pre-release version will work perfectly, it's possible that it's because of the outdated version of the atmosphere, but I wanted to ask someone experienced in modding Nintendo Switch if I'm wrong and if I just messed up the memory of the switch
@@sthetixofficial Thank you for your answer, and I have one more question. I didn't update emummc and I noticed that there are files wb_13 and wb_14 in the warmboot_mariko folder, I don't know if it will cause problems after updating emummc to 19.0.1 and after updating ofw in emummc I had a warmboot error and I fixed it by deleting and installing hekate, I don't know if it's may have created a second warmboot. I would like to ask you for an answer because I am very worried and I don't know if it is a serious problem!
fuse mismatched that is why your console cannot boot to the OFW. you need to downgrade your console to any firmware, then update your console online to burn the efuse.
i have try this 3 times no luck it wont boot to ofw firmware (black screen) semi stock (black screen) cfw sysmmc (a fatal error occurred when running atmosphere error desc std:: abort() called (0xffe) 😥😥😥
Yoooo STHETIX! Finally got it working after so many tries thank you However there’s a lil problem I can load in to emummc but not ofw or sysnand any thing I can do ? Thanks bro
just dump your emummc using hekate, after you get the boot0 boot1 and the emummc dump data, move it to the correct restore folder inside the sd card and later restore it again using hekate. try to watch ua-cam.com/video/sXcfvb47raY/v-deo.htmlsi=de-Qdr9m-tabHuRc
Hello friend, l'm a technician and I also do mods on Nintendo switch oled consoles, a strange fact happened to me, the NX v6s chip no longer turns on, the console connected to the 0.500A power supply, I have already checked the soldering points with the multimeter and they are all pertectly connected, I connected the console to the PC and it is not in RCM block, the 5V arrive regularly on the charging connector, what could it be? I would be very grateful to you! (The DATO is permanent) thank you
I also have the same problem, console type is V1 unpatched. I used the 32GB donor file, the generated rawnand.bin is 256 MB and cannot be opened by NxNandManager
@@sthetixofficial I tried with version 1.0.0, but when the Nintendo logo comes up the screen stays black, I don't know if it's because the board has more faults, the fuse number is 18 and I installed 18.0.0
In my case, the nand got bricked maybe due to hardware defect or bad electricity. I was able to revive my switch using nand module replacement I bought from a*express and sthetix' older guide using donor nand.
FYI, you need to put the donor_rawnand.bin in the same directory/ location / folder as the NANDFIX app, so it will be able to build a complete rawnand.bin either 32GB or 64GB.
I have a problem.
switch OLED Atmosphere Right Joy not connect.
But Joy copy is Connect.
Has anyone encountered this problem? And how to fix it?
Thank you
🎉Congratulations on reaching 100K!🎉
I've been rewatching your 3ds vids and noticed. Thanks for your vids man.
In sthetix we trust.
The nandfix software gives a non-zero exit status regarding the firmware, with the argument -mariko autorcm. Any way I can fix this?
@@karmaknight1411 Same problem, were you able to solve it?
@@alejandrohernandez-cm9hd check author's reply below
I revived my bricked switch with your older guide. This one seems simpler. Thank you for sharing
Still remember watching your videos on how to mod my 3DS, Congratulations on 100K!
thank you
Thank you for this detailed video
Glad it was helpful!
When all hope was lost i found you 🙏🙏 thank you!
Happy to help!
as usual, sthetix has another great video tutorial! thank you! 🇵🇭🎮🇮🇩
You are a legend! Great tutorial 👌
Excellent guide, thank you very much
we learn from the best of best 🥰🥰🥰🥰🥰🥰
hello frend yours tutorials are amazing thank you very much !!!!!
Woah, now you can unbrick it too!
I hope i want need it but when i know where to look up the solution. BTW really greatfull for your guides. Helped me a lot in the beginning. The Switch lite and oled works like a charm :)
Great!! 😎👏👏👏👏 thanks!!
Good job buddy! also people should know that this should perform faster than previous methods as user decrypt and encrypt are minimized in size, it also decreases the free space requirements by a factor 2. Excellent! 👌👍
no bro ..no no no..i've modified the algorithm so it cut the user partition to be about 250MB only so it wont take much space.
@@sthetixofficial for the decrypt and encrypt methods? The final donor rawnand will still be the full size right?
for decrypt, i limit the user to 250MB only. and later of course you need to contain the rawnand that is 32GB or 64GB, so you need a large harddrive.
FYI encrypt took the same size, so yes 250MB.
so yes, by using the nandfix, it wont take much space.
@@sthetixofficial thanks for the clarification! Not only you made it take less space, you also made the procedure faster. This is clear now and it's even better! :) great work buddy!
Thank you very much for your help. It worked on my Diablo switch that stopped turning on.
Glad it helped
I don't even have the switch (yet) and, I don't think that I ever have to do this but, I think you're cool 😎.
Great tut 😎
does this work with 19.0?? it will not show 19.0 on confirm fw screen, and the nand im rebuilding was from a switch with 19.0 fw
you can . it is just the nxnandmanager that is not detecting the 19.0.0 fw, but i've updated the link
Thank you 👍🏾
OMG This is so much easier!!!
After building a new NAND , I always get version firmware not found, what's wrong, please help
logre reparar la nand de la switch v2 averiada. compre una memoria sd nueva y una emmc por aliexpress. segui el tutorial exactamente paso por paso excepto por una cosa, primero formatee la sd en exfat y luego introduje la ultima version athmosphere, seguidamente segui todo el tutorial y consegui arrancar la swich en modo HOS. muchas gracias por todas las herramientas.
I managed to repair the faulty NAND on my Switch v2. I bought a new SD card and an EMMC card from Aliexpress. I followed the tutorial exactly step by step except for one thing, first I formatted the SD card in exfat and then I inserted the latest version of Athmosphere, then I followed the entire tutorial and managed to boot the Switch in HOS mode. Thank you very much for all the tools.
You are welcome and glad it worked!
My switch is on the technician after I try update. He call me saying is bricked can't found nand. He will work on it all night and call me tomorrow. I hope he know about this method
thx for the app. it saves time by no having to click "yes" a bunch of times. would be nice if you could merge the, generate, decrypt,encrypt and build button into a single button so one can leave the pc and do something else while the new nand is beeing build.
yes I can do that but the potential error would be greater. let's see if I could do that later.
Consegui recuperar um switch v1 com esse vídeo muito obrigado!! Vc e top parabéns pelo oh vídeo.....
You are welcome.
Hello, like always your videos are the best, good explanation and quality. However, I have a question, I have a backup of my old Switch and want to restore that Nand into a switch that I replace de Nand chip (its blank) want to do it with that not with the donor Nand. on the donor Nand can't play locally monster hunter.
Hi sthetix. Great video! I'm having this issue with eMMC partition table empty and I don't have a sysNAND backup. However, I found a PRODINFO file backup from the atmosphere folder, but it only has 32kb. This PRODINFO file can be used with you unbrick method? In that case, I would recreate a NAND from donor and use this PRODINFO from the atmosphere folder?
Another question, my emuMMC is still working just fine. Can I restore my sysNAND with the emuNAND .bin files? Or the PRODINFO from emuMMC can't be used?
32Kb is not a prodinfo file. you need to follow the video from the begiining. your console cannot re-access the eshop again.
This could Work for a Switch 1.1 With error 2153-0321?, the error appeared after updating the console in OFW mode, and now the console is stuck in 2153-0321 screen always in OFW, however in CFW boots fine.
Dont use this guide to unbrick your console.
Maybe you need to update your cfw pack
Great video!! I was wondering if there is a way to change the nand (emmc module) without having a backup.. can you help me?
that's why you need to follow the guide. you need at least 2 components to make a new nand from scratch, which is the prodinfo and it's prod.keys
I am having some issue when building a new nand extructure, it seems to have a problem with prod key, could you show me some light ?
prod.keys, did you get it from the console?
any news if the hats pack will update from "prerelease" to "release"?
i dont know. you need to ask scires.
This was a great video. I'm going to try this on a switch lite that I attempted a mod chip install on. I didn't knock any components off and I think it did something that corrupted the nand. I get a similar color screen when trying to boot the console.
Goodluck
i followed everything to the T but when i restart in ofw its a bright purple screen.. any help?
it could be anything, from your chip, your chip installation, your nand data, etc./
16:54 Wait, so if I follow this guide will I lose internet access on ofw? (for the record, I have a system backup but your restore level 1 & 2 haven't worked for me so now I'm on level 3. Can I get my legit prod key from my backup? If not can't I use a donor prod key and have internet access?)
If you already have a nand backup previously, DO NOT do this guide as you will lose access to the nintendo server, unless you have the original PRODINFO from the console. Prod.keys and PRODINFO are two different thing.
@sthetixofficial I found my legit prodinfo data and am currently still following this guide, is that ok? Will my internet access be ok? (I'm past the building stage. It says 'failed to locate driver files'when attempting to mount rawnand.bin on NXmanager. What should I do? I'll hang to your word for the switch's sake. Thanks!)
@@sthetixofficial I actually found my og prodinfo and created the build, but when I connect the emmc raw gpp to my pc, it can't be recognized and won't work on Rufus. What do I do?
the driver is inside the nxnandmanager folder, please check it out.
@@sthetixofficial ok. thanks. edit: I GOT IT FIXED!. Thank you & God bless you and your tutorials!. Have a merry Christmas!!!
I couldn't manage to repair it. Could it be that it doesn't work in version 19.0.1? I repaired 3 consoles a long time ago, but with the previous video, could it be that it doesn't work in the new version?
I carry out all the processes and I can even restore the boot0 and boot1 files but when I want to start it does not turn on.
I hope you can help me, thanks in advance
maybe you did not do it properly. the guide is working and tested. old guide uses the same concept.
hi, thank for your videos, i has made some of then before, this time im following the guide carefully, and i cant boot the console, im getting black screen. i can use this new generated rawnand to flash my console from scratch with the older level 3 method? or how i can do it? btw, i have an 2019 mod chipped console...
old method is the same as this one..
@@sthetixofficial hi, thanks for your response, my problem is i has been formatted the console's nand, i deleted all in there, in this case may i follow this guide and let the rufus complete all the copy? or how i can fix it?
Hey i came from your shader cache video. Is there shader cache available for witcher 3?
no i dont
I'm trying to follow the tutorial but at minute 4:41 it won't let me use the option (build prodinfo file from donor) why could this happen and how can I solve it? thank you so much
is your prodinfo decrypted or encrypted.?
@@sthetixofficial I don't know how to figure that out, I only got to that part of the video and I couldn't continue because the (build prodinfo) appears in black and doesn't let me choose it, do you have any idea what I might be doing wrong? thank you so much
you need to follow the guide throughly ,it should work fine, unless you had errors
@@sthetixofficial thank you very much for responding
Hello - fingers crossed for this one. Running into an issue - when I run "prodinfo_gen" "Build PRODINFO file from donor" remains greyed out. Any ideas?
make sure you have put the donor.keys and the donor_prodinfo.bin and the prod.keys inside the switch folder
@@sthetixofficial That was the issue, thanks!
My console has never been banned before following your guide, after repairing the nand can I safely connect my switch to the internet or will I immediately be banned?
this guide will make your console similar to banned
So this only works in cfw? What happens if you try and connect to online services in cfw now the sysnand is clean? Does it just say "restricted". I assume so?
And I'm assuming you can't just get an unbanned serial to use with prodigy? Would that risk the other console getting banned?
this is for those who want to unbrick their console without the nand backup and in the end it will make your console the same as banned.
I already resurrected a V1 with dead NAND using your old guide, after getting a new NAND module from Aliexpress. Is there any advantage in following this new method again?
advantage = faster and less human error mistakes
@@sthetixofficial for a new console to resurrect that's for sure, but what about a console already resurrected with the old method? Any advantage to use this new procedure again?
no advantages over the resurrected console.
managed to get 2 bricked switches up ... however after revival they are not detected on PC for USB installation of NSP.. any ideas?
i think it has nothing to do with the USB installation, please try using DBI with MTP responder method.
@@sthetixofficial that's what I thought too but two machines in a row now.. USB picks up perfectly fine In Hekate and I'm able to browse the SD card and the emmc raw gpp but when it goes into cfw it stops detecting usb. Will just charge.. if you can test a system and let me know that would be great
@@sthetixofficial and even with MTP responder it fails to detect the USB.. like as if there's no USB connected just a charger
maybe you should edit the usb 3 feature on the hekate_ipl and the system_settings.ini on atmosphere config folder.
is it possible to create with the LVL3 unbrick a working emunand if the emmc is damaged?
You dont need to do the level3 if you have a working emunand. Just dump the emunand and flash it to your console.
@@sthetixofficial The emunand is not yet set up and the emmc seems to be broken. It would be great if i could bring the Switch back to life with an emunand, even with a defective emmc.
just do the level 2 guide
I followed the tutorial and it can’t find boot 0 and boot 1 do I need to create a emmc partition?
you need to simulate the backup first and put the generated boot files to the restore folder as in the video
Gracias Men. ya ocupaba una guía así.
tengo un par de dudas espero algún Dia las puedas responder.
1. Si mi Switch le instale Magia, y al iniciar el ofw se queda en el segundo logo de Nintendo switch. ocuparía hacer esto oh con reinstalar el firmware con sus prod keys. se solucionaría*
2. Digamos que hago lo anterior de dumpear las keys y prod que trae la consola. Restauro la nand donante y uso las keys y prods originales*. conservo el online o al terminar el proceso la consola quedaría en pantalla negra o iniciaría normal*
if you have the original console prodinfo and prod.keys you can generate a new nand using the tool
Is it important to which firmware i choose for this method?
My previous nand compeletly destroyed and i have no access to firmware .so i replaced nand chip with new one . With all firmware on this method i get black screen on ofw & cfw.
you better use at least 18.1.0 firmware
Same thing here. I followed all the steps and everything went through without errors but still black screen on ofw and cfw. Android and linux run fine. Did you manage to figure out what the issue is?
Hello, can you make a tutorial on how to transfer a save file from emunand to sysnand? Thank you!
My picofly switch is no sd without sd, blackscreen with sd and bsod when + and - together with power button. How can I launch into hekate? is there somethiing wrong with my installation?
replace your SD card with another brand. or did you use any cfw pack? if not, please try using my pack, www.sthetix.info/hats/releases
today when I restarted the cursor to hekate, there was a troll face instead of the cursor and the steering was reversed. maybe you know how to fix it. I don't know what could be the cause of this because I didn't install anything. 😭pls help😭
try to delete the existing atmosphere/bootloader/config and extract my pack.
It is possible only change the color of my NS?
use the prodify app but why?
Hey, thanks for nice and clear video, mine is bricked cant enter into any sys(oled modded), but when i tried backup it came to 97% and aborted. In one video you said any backup is good, so im not sure which level/video to follow for unbrick, any recommendations?
as long as you have the prodinfo intact you can follow the level1. or level2.. you can use this video guide too but substitute the prodinfo with your console's prodinfo
@@sthetixofficial Nice thank you, i will then probably use this video with my prod.keys
@bhMaker963 prod.keys and prodinfo
I'm about to do housing for my switch lite and is not banned is it possible to extract my prodinfo and use prodify to change the color without ban?
DO not edit the prodinfo with Prodify or you might get banned. This prodify app is for banned consoles only.
@@sthetixofficial understood, thank you, I appreciate your tutorials
Thank you for your work 💪 I have an Oled which has a freeze problem. After launching a game, the switch freeze after the loading screen or after 2-5min of playing. With cartridge or backup, same.
Some big game run just fine so I think about sysnand and restore it, level 2, same.
Reball emmc, checking short, everything is ok.
Maybe you have an idea ?
Thanks you boss 💪
try to replace the cpu, i guess the Soc is damaged or at least try to replace the ram chips
i have a mariko switch with (probably) defective emmc. The switch does not boot at all, and I also have a missing 1.3V rail. I have an empty nand and would now like to implement this guide. But if I see correctly, I have to install a picofly to get into the hekate at all, right?
you never alter the nand as you are over thinking. Just repair the hardware, power side, please use the xzz platform to check the diode value
@@sthetixofficial console is in rcm mode, would this not be emmc?
you need to know if it is a V1 or V2 ?
@@sthetixofficial v2 mariko
@@sthetixofficial v2 mariko
Interesting tutorial thanks, I'm using a windows arm version (because of running it under vmware on macbook m3) and I'm stuck at the "Encrypt" step of NANDFIX ! Unfortunately it's not doing anything and I have no logs of what it is supposed to do, so I can't find what is going wrong. I tried to check NANDFIX source code to see but it's not available :( Could you tell what command is ran by the encrypt button ?
Edit : it seems it is using the NxNandManager encrypt feature, I'll try to do this step manually to progress ...
Edit 2 : The dokan driver to mount partition doesn't seems to work on arm64 windows :( I'll find a x86 windows then ...
you cannot use the windows ARM version.
@@sthetixofficial I've just tried using a x64 windows 11, and I still have the same problem at the encrypt step with NANDFIX, it says encryption ok but not a single .enc file is created. Runing NxNandManager GUI is working well so I'm not missing any library to make it run ... I used NxNandManager gui to encrypt different files and I'll continue the process to see if it works ...
I use windows 11, x64, and encrypt worked fine.
if it doesnt, then you need to check the prod.keys and the donor.keys file
re-extract the donor rawnand and its donor.keys
Make sure your prodinfo.bin is DECRYPTED , not encrypted, please check it before you do the encryption with the nandfix.
I'd argue that the sysmmc isn't useless in this case. You're already SOL when it comes to connecting to Nintendo servers, so might as well use it to save some games to if you're out of space on your SD card lol
what is useless is the ofw bro. and semi stock.. not the sysmmc
I gave it a try, but it keep showing me the message --mariko returned non-zero exit status after pressing generate but. I would really appreciate any suggestion on this trouble, its my first try on nand problem XD
you need to use dot net 7.0.2 bro.
@sthetixofficial yeah, seems like my atom based laptop doesn't work fine with Microsoft services. I tried on different PC, and succeed with it. Thank you very much on simple and clear instruction!
I'm still sadly surprised that anyone hasn't have Hack the Nintendo Switch version 2 yet.
Picofly
Software? Not.. Modchip 👍🏻
There's no reason to release a software hack that will surely get patched as soon as it drops when we have unpatchable hardware vulns
Sthetix has videos on how to mod the V2
it is on my yt channel
I have NS and is SN is XKJ, this still not have CFW and homebrew ?
all switch are hackable, use a modchip instead.
@@sthetixofficial I searched your videos but didn't see how to do it, do you have instructions to do it?
ua-cam.com/video/J7NfQ3fdNsI/v-deo.html
@@sthetixofficial thanks 🥰
The nandfix software gives a non-zero exit status regarding the firmware, with the argument -mariko autorcm. Any way I can fix this? I have retried the lockpick rcm script several times, yet the error in nandfix always reccurs. What do I do?
as stated in the video, you need to USE the dot net 7.0.2, not more, no less
@@sthetixofficial thanks man
@@sthetixofficial Now when the nands are fully combined the firmware version cannot be found. Before combining, specifically the system partition, the firmware version was shown as 12.0.2 (wrong one, as I use 15.1.0), but after it shows FW not found. Everything else seems fine, like the serial number created via prodify. When the boot0 and boot1 are loaded onto the switch, the size of the SD card backup does not match eMMC's selected part size. If I continue, the Nintendo logo flashes then turns black if booted into OFW, and the processor gets hot. I have repeated the process with several firmware versions, and only the 15.1.0 has resulted in this, others made blue screens. Any way I can fix this?
you can try to redo the guide and use 18.1.0 firmware
@@sthetixofficial As I have previously stated, any other firmware results in a blue screen. The 15.1.0 is the only version that even gets a Nintendo screen. I believe that the prodinfo is the culprit, as it is responsible for displaying the firmware version, though I don't know for sure. Is it time to give up?
Dont know why, but if you use a higher firmware like 18.0.1 and the console has an old firmware installed, you get an error on the Generate button. my faulty emmc console was on fw 17.x.x with burned fuses to these firmware. maybe the generated keyfiles dont match with the files of higher firmwares in these case?! Only Guessing!
keyfiles are intact, But maybe the firmware files arent right? where did you get the firmware files?
@@sthetixofficial from your Page. The latent 18. In the list. Process is working atm. Only nxnandmanager seid unknown firmware after Import the emmc files.
@@sthetixofficial Strange, i already answered yesterday. Got the firmware from you page. the latest 18.0.1. / Used now the 17.0.0 and works fine. Good solution and easier as the last nsw 3 ;) The old serial number in the system is great ;)
you can omit the unknown as it is just a status. you can udpate your working nand with new firmware as usual using Daybreak.
I have a problem.
switch OLED Atmosphere Right Joy not connect.
But Joy copy is Connect.
Has anyone encountered this problem? And how to fix it?
Thank you
x.com/sthetixofficial/status/1659762665198329858
Hi there Man, afterusing the level 2 and not suceeding, now I am trying the level 3 with my original prodinfo. But the Nandfix pop out an error saying that "The loaded prodinfo is encrypted, cannot proceed". Is there any other way to goo around this ?
you need to decrypt the prodinfo first, by opening it using the nxnandmanager along with your keys then decrypt it and save it
@@sthetixofficial Thanks man, after following your guide, it can be done. The only problem left is my switch only show the Nintendo logo and proceed with blank screen.
On that note, after restoring the EMMC boot0 and boot 1, there is a prompt that pop out saying that EMMC in slow mode.
Is it possible that my NAND Chip is broken?
it could be affected on the chip you are using. usually Pico
@@sthetixofficial Yes, it is picofly chip.
If so, then do I need to replace the pico chip or the NAND chip
@rajikkumastah452 replace the Pico with a proper one, like the instinct-nx
I followed the steps to the letter, then when I reboot>ofw the Nintendo logo comes out and then it stays on the black screen. The switch worked fine, I had it installed the chip and now only the CFW mode works, any idea to make the OFW work?
Check the fuse count bro..maybe it mismatched.
@@sthetixofficial in that case, what should I do? this is the information : Burnt Fuses (MDG 7/6): 20 | 0 - HOS 19.0.0+
what is your console firmware currently?
@@sthetixofficial Currently in the emummc system I have the 19.0.0 with atmosphere, and I followed your video with firmware 19.0.1 and it still doesn't work, nintendo logo appears and then black screen, I made an emummc of my current nand and run it in CFW and it works, it starts as if I was just bought the console, so I guess it worked as such, only when running sysnand it does not boot, only with CFW
@@sthetixofficial By the way, thank you very much for taking the time to answer me, I appreciate it very much and apologize for the inconvenience.
I did the procedure several times! My Switch works again, but if it goes into standby, the Switch hangs and doesn't return.
fuse mismatched. if yours is a V1, disable the autorcm.. and reboot to ofw.
@@sthetixofficial Mine is the Oled, I follow the video exactly as you do, but when I try to enter OFW it takes 15 minutes for the Nintendo logo to appear and then another 15 to 20 minutes to start the system, then with the system working if it enters stadby it freezes, having to turn it off and on again.
there is something wrong with the chip or something else. or bad sd card, etc.
@@sthetixofficial I managed to solve the problem, I noticed that there were some markings on the Switch board, I believe that this console was remanufactured, so I did reballing e o Switch voltou ao normal. So I put back the original Nand backup and it went back to normal, in fact after the reballing it was already normal, but I wanted to go back to the original prodinfo
I tried the tutorial 3 times. After the nand fix build task, nxnandmanager says ( fw ver: Not found).
Note that I skipped the the prodify steps because you said it is just aesthetical.
Any help?
FW file not found doesnt mean the nxnandmanager is faulty, but maybe you did not download the nxnandmanager that can detect 18.1.0 firmware or later.
try this www.mediafire.com/file_premium/x4unhcftn8er945/NxNandManager_v5.2_x64_18.1.0.zip/file
What firmware version did you use when Generating the NAND files?
@@sthetixofficial I used 18.01 and lately 18.1
it should always can detect the FW version, but that is not important, the thing is if the app succesfully generated the 32GB or 64GB rawnand.bin then you can flash it to your console.
I downloaded the nxmanager in the link and now it is showing the correct fw version.
But I ended up with a black screen and modchip not glitching anymore until I disconnect the battery.
I even deleted the .bin extension on the bckpkg , still black screen.
Maybe hardware issues, I dont know what to try next
Sorry, normal time decrypting? I wait 1 hour
No, it is not suppose to be like that.
hi, i have problem when mod v2 using picofly
2002-3540 on the brand new v2
synthomp : using daybreak for update the ofw, and failed cannot 100%, after this, ofw and sysnand many times will show 2002-3540, sometimes can boot normally
im technician on mod switch, thanks
You better discard the pico, as that chip mostly causes the issue. Use a proper chip like the instinct-nx
@@sthetixofficial i will consider it, but what should i do when error code 2002-3540?
i dont know, but just remove the pico first, because that pico is..poisonous
@@sthetixofficial hmm okay, but it is safe to update the ofw using daybreak in sysnand? or use daybreak only in emunand?
daybreak is fine on sysmmc and emummc
when I click generate it fails?
Hello Sthetix .. Please could you help me, my console is a demo console that is in stores. the format and I got this message (Could not start the software). Can you revive my console.. Thank you..
i never had any demo console so I dont know the solution.
will online work after this level 3 unbrick?
online to other server rather than nintendo = yes!
@sthetixofficial oh, i meant nintendo servers...
cannot. as i stated in the video, if you did the level3 , then it is the same as banned, because you dont use the original console prodinfo
thanks
After trying this and the old guide my V1 Switch still doesn't boot it shows the nintendo logo and then black.
Same for CFW or semi CFW.
make sure to choose the correct console type, Erista / Mariko, try launcing the sysmmc cfw too
@sthetixofficial I have done both.
I don't even get an error when booting into atmosphere it just shows the logo and then black.
And I think atmosphere gives you an error saying you installed the wrong console type if im not wrong but in my case it just goes black.
@sthetixofficial Could corrupted keyblobs stop it from booting?
@tamash2140 did you create the erista nand files?
have you checked the generate nand and check if it could be opened using your prod.keys?
When the new hats pack drop?
it is there, www.sthetix.info/hats/releases/
Tinfoil now doesn't work but everything else is good. Do you know how to fix it?@@sthetixofficial
hi when i copy the data in the nx manager in system when re open de .bin not found fw Version
maybe you need to check the steps again
@@sthetixofficial i like you time to dedicate make this tutorials ... i been try 3 level of this but i cant run the nintendo .... just only can boot in hekate. i have v1 unpatched consolte whit full wiped sysnand
did you see the fw version when you open the nand on the nxnandmanager?
@@sthetixofficial yes , now i try to make the same proces again whit fresh download folders and more
in the other side its normally when i go flash whit rufus v1 unpatched rawnand.bin says in the partition scheme GPT ? target system uefi ( non CSM ) , Cluster Size 16 Kilobytes and File System Fat32 i said this for in the video in minute 14:48 its like different
is there any way of linking nintendo accounts on this sysmmc w/o getting banned
if you did this guide. then you won't be able to link your nintendo account legitly. unless you use the original prodinfo and your console is not banned yet
@@sthetixofficial so is there no way to get my saves and purchased games from my Nintendo account
@@sthetixofficial do you think my emummc prodinfo would work since it's basically a copy of sysmmc
of course it will
I recently updated ofw to 19.0.1 along with hekate update to 6.2.2 and ofw works normally after the update but blue screen appears on the current stock. I didn't update the atmosphere to 1.8 because I'm not sure if the pre-release version will work perfectly, it's possible that it's because of the outdated version of the atmosphere, but I wanted to ask someone experienced in modding Nintendo Switch if I'm wrong and if I just messed up the memory of the switch
you need to use the prerelease pack..as older pack will cause you blue screen
@@sthetixofficial Thank you for your answer, and I have one more question. I didn't update emummc and I noticed that there are files wb_13 and wb_14 in the warmboot_mariko folder, I don't know if it will cause problems after updating emummc to 19.0.1 and after updating ofw in emummc I had a warmboot error and I fixed it by deleting and installing hekate, I don't know if it's may have created a second warmboot. I would like to ask you for an answer because I am very worried and I don't know if it is a serious problem!
I can one my console dyy but I met new problem which is Failed to match warmboot with fuses! If you continue, sleep wont work!
and the last step you do which is restart to ofw on hekate mine is black screen but when i press stock sys and press continue can on but cannot sleep
fuse mismatched that is why your console cannot boot to the OFW.
you need to downgrade your console to any firmware, then update your console online to burn the efuse.
i have try this 3 times no luck it wont boot to ofw firmware (black screen)
semi stock (black screen)
cfw sysmmc (a fatal error occurred when running atmosphere
error desc std:: abort() called (0xffe)
😥😥😥
how did you brick it?
@@sthetixofficial this one have rcm brick
you need to press and hold the power button for 12 secs and try to reinject the payload
@@sthetixofficial thx for help there the fuel gauge ic are defect its fixed ens working fine :)
Yoooo STHETIX! Finally got it working after so many tries thank you
However there’s a lil problem I can load in to emummc but not ofw or sysnand any thing I can do ? Thanks bro
why dont you dump the emummc and flash it to the sysmmc
@@sthetixofficial how do I do that
@@sthetixofficial I need ofw but only cfw emummc works? Help please brother
just dump your emummc using hekate, after you get the boot0 boot1 and the emummc dump data, move it to the correct restore folder inside the sd card and later restore it again using hekate. try to watch ua-cam.com/video/sXcfvb47raY/v-deo.htmlsi=de-Qdr9m-tabHuRc
error
input file/drive is not a valid nx storage
read the pinned post bro.
How to transfer sysnand save data to emmunand
please watch my jksv guide
Bang saya maen game terbaru kok dia nanya apakah game ini butuh internet. Ga bisa maen
tergantung gamenya, mungkin harus pake linkalho
fix error 2002-4687 ofw , notchip , enter sysnand not error , not update daybreak
i dont know what you mean.
Hello friend, l'm a technician and I also do mods on Nintendo switch oled consoles, a strange fact happened to me, the NX v6s chip no longer turns on, the console connected to the 0.500A power supply, I have already checked the soldering points with the multimeter and they are all pertectly connected, I connected the console to the PC and it is not in RCM block, the 5V arrive regularly on the charging connector, what could it be? I would be very grateful to you! (The DATO is permanent) thank you
you need to know that Rcm is not available on oled. is your ofw working?
No, the console doesn’t start in ofw, it always stays at 0.500a Could it be the corrupt nand?
no. did you ever reflow the nand chip?
No, for the DAT0 As usual I perform the kamikaze method,The nand is not touched…
check all altered solder points.
Can I ask? Will I have banned for this or not?
This guide is intended for unbricking the console. Using the PRODIFY could ban your console - Do not use it on normal console.
Bro, can you make a video on how to unbrick a 3ds with blue screen of death
you can try to unbrick it with the ntrboothax
@@sthetixofficialwhen I get into safeb9sinstaller it get stuck into the micro sd card checking
not working .rawdump 256mb. nx not open rawnand
I also have the same problem, console type is V1 unpatched. I used the 32GB donor file, the generated rawnand.bin is 256 MB and cannot be opened by NxNandManager
you need to put the donor_rawnand to the SAME folder as the NANDFIX, i've stated it in the video.
you need to put the donor_rawnand to the SAME folder as the NANDFIX, i've stated it in the video.
@@sthetixofficial thanks for the clarification
I wish there was still easily available 64GB to 256GB V1/V2 NAND daughterboards.
you can create it yourself.
Hola, estaba usando tu programa y automaticamente windows me lo a eliminado y lo ha metido en cuaerntena como un virus, pone que es el trojano bearfos
you need to disable your antivirus or disable scan on the Exe file..
Microsoft just added a weird detection method. I got the same message recently
@@sthetixofficial I tried with version 1.0.0, but when the Nintendo logo comes up the screen stays black, I don't know if it's because the board has more faults, the fuse number is 18 and I installed 18.0.0
@redodc6152 why did u use 1.0.0?. u. need to use the latest firmware
I used the same firmware you used in the video, but I used version 1 of nandfix from your github, on the switch I used version 18.0.0
any version is detected by microsoft as trojan now, even mine.
How does one destroy the nand like this?
by following another sthetix guide
no offense to sthetix, he warns people ;)
In my case, the nand got bricked maybe due to hardware defect or bad electricity. I was able to revive my switch using nand module replacement I bought from a*express and sthetix' older guide using donor nand.
Still stuck on Nintendo Switch Logo. How sad
oh wait. emummc boots but not OFW and semi-stock
you can just dump or backup your emummc, then flash it to your sysmmc, no need to follow the guide.
Galera cadê os links 😢
what links?
@@sthetixofficial desculpa era like
I am sorry i dont understand
nandfix give my a error it wont generate 😭😭😭
what error?
@@sthetixofficial an error occurred during nand files generation command
(mariko returned non_zero exit status 1)
as said in the video, you need to use the dot net core 7.0.2, not higher, not lower.
my rawnand build 256mb only
bonjour je cherhce un tuto en francais ma switch es briker ecrant bleu
Try watching my level1 unbrick guide
Solution You can solve the problem of Nintendo ban
yes if I were the owner of nintendo
rufus error Erreur: Erreur d'écriture.
maybe you did not enable the write option.
This channel is Amazing. Wow 🫨