Hacking Question Switch keep waking up from sleep mode

  • Thread starter Thread starter Deleted User
  • Start date Start date
  • Views Views 8,356
  • Replies Replies 29
Restoring the NAND is as easy as sticking your rawnand.bin in the restore folder made by Hekate, loading Hekate, then selecting restore eMMC raw GPP.
Fair enough, forgot about hekate, but still, this first
Can I try to rebricc the fuses even if they are bricced? I wonder if the problem has something to do with the bricc that ChoiDujourNX uses, so I'll try using briccmiiV2.
I want to avoid removing autoRCM and activating again because I don't have a jig, and using tinfoil isn't reliable in the sense that it may not be well positioned, causing the console to normal boot.
 
After you restore the NAND in Hekate, you can choose the Reboot to RCM option then send briccmii V2 as a payload to see what the bricking status is and move on from there.
But I want to try rebriccing them now, before restoring the NAND. Is it possible, or will it have any complications?
So, basically, they already show as bricced, which was done with ChoiDujourNX, but I want to do it again with briccmiiV2 WITHOUT debriccing first.
Also, as I said, I upgraded from 4.1 to 5.1 with fuseless method. I take it that restoring the NAND that has the 4.1 won't cause any problems apart from all of the already installed games being unplayable, right?
Sorry for being a pain in the ass. I just wan't to be sure nothing happens to my console and want to avoid long time consuming processes.
 
But I want to try rebriccing them now, before restoring the NAND. Is it possible, or will it have any complications?
So, basically, they already show as bricced, which was done with ChoiDujourNX, but I want to do it again with briccmiiV2 WITHOUT debriccing first.
Also, as I said, I upgraded from 4.1 to 5.1 with fuseless method. I take it that restoring the NAND that has the 4.1 won't cause any problems apart from all of the already installed games being unplayable, right?
Sorry for being a pain in the ass. I just wan't to be sure nothing happens to my console and want to avoid long time consuming processes.
I bricced my console using ChoiDujourNX and it looks identical to the one used in briccmii when I loaded the briccmii payload. I honestly don't know what will happen if you try to bricc the console again using briccmii V2 (which briccs identically to briccmii V1) but generally its not recommended to bricc the console using multiple forms of AutoRCM. The reason for this is because it'll make the unbriccing process more complicated and possibly irreversible. If you are fine with that risk, you can try rebriccing the console with briccmii V2 before removing the bricc performed by ChoiDujourNX. Also, depending on what was installed in that 4.1 NAND, certain things will not work if you installed them afterwards. I would recommend backing up the saves at the very least as all of the other data that is not stored can be retrieved online. Lastly, to quell any other doubts when you restore the NAND, it has no bearing on AutoRCM since it affects the boot0/boot1 of the console instead of the raw GPP which is comprised of SYS and USER.
 
So, I was just going to restore the NAND, boot0 and boot1, but I don't have a numbers and letters folder inside the backup nor restore folder. I only have the files... Can I still restore it?
 
So, I was just going to restore the NAND, boot0 and boot1, but I don't have a numbers and letters folder inside the backup nor restore folder. I only have the files... Can I still restore it?
If you run Hekate V4.1 once, it will automatically generate the proper folders for restoring. Do that and then put the files in the right place(s) accordingly.
 
If you run Hekate V4.1 once, it will automatically generate the proper folders for restoring. Do that and then put the files in the right place(s) accordingly.
I did so. Restored the NAND and BOOT0 and BOOT1, still had the problem. Factory reset, still had the problem, so it was a hardware problem. Just went to trade for another one and I'm currently dumping the NAND.
I was also told to not use the dock if I primarily game while docked, because apparently heat makes the connections loose, and it could be from that. Might grab a female to male USB C adaptor and let it sit outside the dock.
 
I did so. Restored the NAND and BOOT0 and BOOT1, still had the problem. Factory reset, still had the problem, so it was a hardware problem. Just went to trade for another one and I'm currently dumping the NAND.
I was also told to not use the dock if I primarily game while docked, because apparently heat makes the connections loose, and it could be from that. Might grab a female to male USB C adaptor and let it sit outside the dock.
I updated my switch to 6.1 and had the same issue. The console would not go into sleep mode, it kept turning back on. I came up with a solution that worked for me.

Go into settings and disable airplane mode. Put the switch into sleep mode and that's it. Worked for me.

Also, you can enable airplane mode but also enable the option to connect via bluetooth with the controllers. Give it a shot.
 

Site & Scene News

Popular threads in this forum