Hacking URGENT! Console Bricked. Stuck at Switch LOGO

[Emeraldman94]

Help. I HAD a 6.1 sysNAND and 6.1 emuNAND. Never used sysNAND. Only made backup of 4.1 sysNAND before hacks

the Switch boots up into RCM mode. Then I click emunand or custom firmware. Then the Nintendo screen flashes. Then Black screen. Then Nintendo Switch screen. IT then freezes on this screen and never moves on. I noticed this after I installed a fire emblem game update and DLC from a site I was pretty familiar with. Once I backed out to home screen it froze. Then my switch could never turn on properly.

I turn off my switch my holding the power for 15 seconds. Charge the SX pro. Then try again and always get the same results.

Auto RCM was on. I turned it off just in case.

Booting into Original firmware doesnt work anymore EITHER!!!! I never used original firmware

Even though AutoRCM is off, If I turn on the console without dongle, RCM jig and SD card it wont boot up. screen doesnt even light up.

I used Hekate to restore my eMMC BOOT0/1 and eMMC RAW GPP (Exfat only) from my original backup. It still doesnt work. RCM is uninstalled. Booting the system with no SD card, No SXPro dongle, and No Jig results in No boot.

Booting into CFW from SXpro still has same Nintendo Switch logo hang. HELP

I thought it was a fuse issue since I have burned 7 fuses (6.1) but restored to 4.1

However I followed the guide (https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/)

And patched it to 4.1 including BOOT0/1 that didn’t work. Then tried patching to 5.1 and 6.1 that didn’t w ork and I didn’t even see the switch logo when I did those.

Im lost for what to do really. Booting into Hekate then loading Original FW doesn’t work. Loading CFW from SX OS and Atmosphere payload still hangs.

Also I noticed when I dump my keys BISKey2 and 3 are both the same. Not sure if that matters.

Hekate also shows TSEC Key 3 as 0000000000000000000000000000000

Looking back Im not sure how I dumped my NAND if it was using Hekate or the SXOS NAND dump. I had a 15 piece NAND file .00-.14. Then merged them to do the restore using Hekate. (Not sure if that matters) Maybe they were joined bad by the joiner (they are the exact same size, but maybe not in same order) Also how did I get the 15 pieces? Is there a NAND restore that will restore using the 15 pieces? Maybe this isnt even the problem. Im also wondering if SD format is a problem. Im using ExFAT, but also have FAT32. Not sure what I should be using in this pretty sure I tried both, but maybe Im messing up there.

What do I do?

 

[iriez]

Don't lose hope but I had this same issue and it was hardware related. I have seen others with the same issue. Switches can and will have hw failures and annoyingly it still works in rcm, backups restore, etc.

The restore nand is probably ok, the parts bit is a fat32 solution. Hekate will rejoin them for you automatically.

 

[MeteK]

Why is it urgent ?

 

[Emeraldman94]

Don't lose hope but I had this same issue and it was hardware related. I have seen others with the same issue. Switches can and will have hw failures and annoyingly it still works in rcm, backups restore, etc.

The restore nand is probably ok, the parts bit is a fat32 solution. Hekate will rejoin them for you automatically.

So what do you think I should do What were you saying about FAT? Also Hekate does not rejoin them for me. IT says cannot find rawnand.bin when Its not joined

 

[bk300]

Still didn't fix you switch yet? I almost see you start new thread everyday.
Try this;:
1.boot into RCM mode.
2.hold the Volume Up + Volume down at the same time.(hold both button until it fully boot up)
3. Inject the ReiNX.bin.(for boot up only)
Ok. on step 3. Inject the ReiNX.bin.
Link:https://github.com/Reisyukaku/ReiNX/releases
After that it should boot in to "Recovery mode" than do the "Restore factory settings". Or upgrade to the last firmware.


If still doesn't work the only thing you can do just
Use ChoiDujourNX https://gbatemp.net/threads/choiduj...ller-homebrew-for-the-nintendo-switch.513416/

 

[Emeraldman94]

Still didn't fix you switch yet? I almost see you start new thread everyday.
Try this;:
1.boot into RCM mode.
2.hold the Volume Up + Volume down at the same time.(hold both button until it fully boot up)
3. Inject the ReiNX.bin.(for boot up only)
Ok. on step 3. Inject the ReiNX.bin.
Link:https://github.com/Reisyukaku/ReiNX/releases
After that it should boot in to "Recovery mode" than do the "Restore factory settings". Or upgrade to the last firmware.


If still doesn't work the only thing you can do just
Use ChoiDujourNX https://gbatemp.net/threads/choiduj...ller-homebrew-for-the-nintendo-switch.513416/

Well I cannot use Choi NX. I dont have access to the Homebrew MEnu since no CFW load up.

Ive tried recovery mode multiple times. using CFW and OFW and it still doesnt work. I havent tried ReiNX. I guess I will try that now.

EDIT: Yea it didnt work. Same switch hang as usual. But when I click volume + and - it goes away to a black screen then hangs there. My SAFE folder is apparently empty. Not sure if that matters

 

[bk300]

Well I cannot use Choi NX. I dont have access to the Homebrew MEnu since no CFW load up.

Ive tried recovery mode multiple times. using CFW and OFW and it still doesnt work. I havent tried ReiNX. I guess I will try that now.

EDIT: Yea it didnt work. Same switch hang as usual. But when I click volume + and - it goes away to a black screen then hangs there. My SAFE folder is apparently empty. Not sure if that matters

Make sure you hold the hold the Volume Up + Volume down at the same time in correctly.(hold both button until it fully boot up)

 

[Emeraldman94]

Make sure you hold the hold the Volume Up + Volume down at the same time in correctly.(hold both button until it fully boot up)

yeah I do that but it never ever works. I think the defect isn't letting recovery mode load.

 

[iriez]

Still didn't fix you switch yet? I almost see you start new thread everyday.
Try this;:

Ok. on step 3. Inject the ReiNX.bin.
Link:https://github.com/Reisyukaku/ReiNX/releases
After that it should boot in to "Recovery mode" than do the "Restore factory settings". Or upgrade to the last firmware.

Why would the reinx take you to recovery mode? Isn't that the bootloader for the CFW?

 

[flatty69]

Why is it urgent ?

cause he needs to pirate that smash bros jeezzz

 

[mikefor20]

You had a 15 part NAND dump and merged them? WTF? That was either a SXOS dump. Or Hekate dump done on Fat32... put the files back how they were. Unmerged and restore with SXOS or Hekate. Whatever you used. I wouldn't guess with this. Never merge them. Why would you do that? The program pushed out a bunch of files and you just had to dick with them. Why do people make up solutions? Then you could try Maintenance mode again. Some BS Nsp you got somewhere shady did this more than likely. Not SXOS. It's more stable than Kosmos..

Don't lose hope but I had this same issue and it was hardware related. I have seen others with the same issue. Switches can and will have hw failures and annoyingly it still works in rcm, backups restore, etc.

The restore nand is probably ok, the parts bit is a fat32 solution. Hekate will rejoin them for you automatically.

I seriously doubt it was a hardware issue in either case. These things are touchy but it's usually software. You all need to stop following YouTube,Reddit ramndom tutorials and stop installing any old NSP.. And label your backups. SXOS_backup_MM=DD=YY_sys ver. christ It's fixable with a proper nand backup.

I had a "Stuck at switch logo at boot" issue. I fixed it by restoring a backup. Every time I updated it got the same logo loop. I updated with a cartridge(no fuse burn method) and with ChoiDuJourNX and consistently got the Logo Loop.<---- (What I call it) Plus my HDD wouldn;t work in SXOS. I fixed it by:

1. Turn off AutoRCM - My fuses matched my Sys Version after my backup restore and I couldn't get Maintenance mode to trigger until AutoRCM was off
2. Boot in to Maintenance mode (Power of completely by HOLDING POWER FOR 20SECONDS. I know it's 12 but just to be sure. HOLD vol + AND - then tap power and keep holding Vol + AND - until boot
3. Select Initialize and keep save and user data

After that ChoiDuJour worked, no logo loop. Plus my HDD worked in SXOS. Something I installed did it I bet. I tinker too. I just read more I guess.... I have tried pegeswitch, rei, raj, atmo, linux, retro, the other retroarc like thing I cant remember the name, All Homebrew I could get a hold of pretty much. I love modding. One of those did it I bet. I think I installed that NSP you are not supposed to install for the SVC patched HB loader too. I didn;t read and comprehend that part that time. NO DRINKING AND MODDING Might be the culprit...

You could just try this earlier in the thread,,

1.boot into RCM mode.
2.hold the Volume Up + Volume down at the same time.(hold both button until it fully boot up)
3. Inject the ReiNX.bin.(for boot up only)
Ok. on step 3. Inject the ReiNX.bin.
Link:https://github.com/Reisyukaku/ReiNX/releases
After that it should boot in to "Recovery mode" than do the "Restore factory settings". Or upgrade to the last firmware.

I don't know if ReiNX's boot loader will ignore your fuse count and trigger Maintenance mode or not but I don't see how it could hurt to try it. Just don't say yes to anything you don't understand. Maybe ill try holding Vol + and _ while injecting payloads and see if they trigger maintenance mode... I'll try after to go to the store and eat.

You could go on the Discord. Ask Raj or someone. They might know.

If you find the solution please post what you did and save someone else the trouble. And stop blaming hardware for bad modding.

 

[isoisoiso]

You had a 15 part NAND dump and merged them? WTF? That was either a SXOS dump. Or Hekate dump done on Fat32... put the files back how they were.

This. Those files were split for a reason. Restore with SX OS and see how it goes.

 

[Emeraldman94]

This. Those files were split for a reason. Restore with SX OS and see how it goes.

You had a 15 part NAND dump and merged them? WTF? That was either a SXOS dump. Or Hekate dump done on Fat32... put the files back how they were. Unmerged and restore with SXOS or Hekate. Whatever you used. I wouldn't guess with this. Never merge them. Why would you do that? The program pushed out a bunch of files and you just had to dick with them. Why do people make up solutions? Then you could try Maintenance mode again. Some BS Nsp you got somewhere shady did this more than likely. Not SXOS. It's more stable than Kosmos..



I seriously doubt it was a hardware issue in either case. These things are touchy but it's usually software. You all need to stop following YouTube,Reddit ramndom tutorials and stop installing any old NSP.. And label your backups. SXOS_backup_MM=DD=YY_sys ver. christ It's fixable with a proper nand backup.

I had a "Stuck at switch logo at boot" issue. I fixed it by restoring a backup. Every time I updated it got the same logo loop. I updated with a cartridge(no fuse burn method) and with ChoiDuJourNX and consistently got the Logo Loop.<---- (What I call it) Plus my HDD wouldn;t work in SXOS. I fixed it by:

1. Turn off AutoRCM - My fuses matched my Sys Version after my backup restore and I couldn't get Maintenance mode to trigger until AutoRCM was off
2. Boot in to Maintenance mode (Power of completely by HOLDING POWER FOR 20SECONDS. I know it's 12 but just to be sure. HOLD vol + AND - then tap power and keep holding Vol + AND - until boot
3. Select Initialize and keep save and user data

After that ChoiDuJour worked, no logo loop. Plus my HDD worked in SXOS. Something I installed did it I bet. I tinker too. I just read more I guess.... I have tried pegeswitch, rei, raj, atmo, linux, retro, the other retroarc like thing I cant remember the name, All Homebrew I could get a hold of pretty much. I love modding. One of those did it I bet. I think I installed that NSP you are not supposed to install for the SVC patched HB loader too. I didn;t read and comprehend that part that time. NO DRINKING AND MODDING Might be the culprit...

You could just try this earlier in the thread,,

1.boot into RCM mode.
2.hold the Volume Up + Volume down at the same time.(hold both button until it fully boot up)
3. Inject the ReiNX.bin.(for boot up only)
Ok. on step 3. Inject the ReiNX.bin.
Link:https://github.com/Reisyukaku/ReiNX/releases
After that it should boot in to "Recovery mode" than do the "Restore factory settings". Or upgrade to the last firmware.

I don't know if ReiNX's boot loader will ignore your fuse count and trigger Maintenance mode or not but I don't see how it could hurt to try it. Just don't say yes to anything you don't understand. Maybe ill try holding Vol + and _ while injecting payloads and see if they trigger maintenance mode... I'll try after to go to the store and eat.

You could go on the Discord. Ask Raj or someone. They might know.

If you find the solution please post what you did and save someone else the trouble. And stop blaming hardware for bad modding.

how do I restore using my 15part backup because I can't get it to work with either SX OS or Hekate. It won't recognize the file is there.

 

[GothicIII]

how do I restore using my 15part backup because I can't get it to work with either SX OS or Hekate. It won't recognize the file is there.

I read a restore is only possible from an exfat formatted sdcard and it must be 1 file. You need to join the 15-part backup with the script from hekate and restore it then.

It wouldn't make much sense to provide the joiner script with hekate when it could handle splitted backups.

https://github.com/CTCaer/hekate/releases

 

[mikefor20]

Dude. Put them in sd/sxos/backup and boot in to sx option

 

[Emeraldman94]

Dude. Put them in sd/sxos/backup and boot in to sx option

I get an error code when I do that. I feel like it's because the files are split. Both Hekate and SX OS never recognize the file when it's split. Any ideas how this apparently works for everyone else?

 

[Psychoticgamer92]

I'm trying this and it says I'm missing a recovery folder? Where can I get one?

 

[Kafluke]

This. Those files were split for a reason. Restore with SX OS and see how it goes.

Yeah the reason is that fat32 doesnt support file sizes over 4gb. That's the only reason. If it was an exfat sd it would dump to a single file.

 

[grozio]

I'm trying this and it says I'm missing a recovery folder? Where can I get one?

i've solved and fix it?

 

[PHiLiPZ]

i've solved and fix it?

Well done?