Hacking Switch will not upgrade.

  • Thread starter Thread starter Philliyxx
  • Start date Start date
  • Views Views 11,171
  • Replies Replies 44
official update = fuse burn, and you should have ban if you booted sysnand...

Wrong. Official update does not mean fuses burn. Fuses burn when the bootloader is run, meaning you can download the update officially but as long as you get into RCM before the console turns on, it won't burn the fuses if you boot cfw.

Trying to upgrade to 6.2 again but switch refuses to boot after upgrading to 6.2 or 7.0.1

Flashed the exfat update upon upgrading. Coming from 5.1 going to 6.2: chose not to initialize. = Reinx and ofw will not boot after restarting switch once upgrade was done.
Restore NAND, 5.1 booting and working again.
Copy over fresh 6.2 firmware files from *cough*. Upgrade, choose exfat, and this time initialize. =Reinx and OFW will not boot. (hang on nintendo switch logo)
Format SD card, try fat32 nothing will boot.
Restore NAND 5.1 booting and working again. This time I get atmosphere to work on 5.1 too.

Upgrade to 6.2 again and choose exfat update, no initialize. =Atmosphere will not boot.
Format SDcard (exfat) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Format SDcard (fat32) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Enter maintenance mode, initialize console.
Boot into atmosphere, get the logo, no nintendo logo black screen and top left corner charging icon, then all black.
Boot into atmosphere, get the nintendo logo, then black screen and no switch logo. Stuck
Boot Reinx 2.0, splash screen, black screen
Format SDcard (exfat) clean install reinx, boot, black screen after reinx boot logo.


Restore 5.1 nand, 5.1 atmosphere 0.8.5 boots fine.
Upgrade to 7.0.1 system initialize option with choidujournx. Switch reboots and get sept boot logo, atomosphere boot logo, nintendo boot logo, and then nintendo switch bootlogo infinetly hangs.
Re-format SDcard(exfat)= same thing.

5.1 nand restore, said fuck it, updated officially to 7.0.1 through the sytem update. SAMETHING, atmosphere doesnt boot and gives fatal error 2021-008.

$$ a brand new sd card from Best Buy, put Kosmos on it, doesnt boot, format and put atmosphere from github on there and doesnt boot. Nothing comes up after nintendo boot screen.

Am I just stuck on 5.1 at this point?!

IMHO you might as well just update and burn fuses to 7.0.1, then try the latest release of reinx from their guide
 
Wrong. Official update does not mean fuses burn. Fuses burn when the bootloader is run, meaning you can download the update officially but as long as you get into RCM before the console turns on, it won't burn the fuses if you boot cfw.



IMHO you might as well just update and burn fuses to 7.0.1, then try the latest release of reinx from their guide
I use SX but Atmosphere is way better on creport and stuff. Reinx is ams made by script kiddies
 
Last edited by pohaxsf,
I have given up. No solution found why my switch can't update to any f.w. past 5.1.
Yes it can..

do you have a backup ?

Store the backup some were safe.
Get the fuse count with briccmii payload..
Once you compare the fuse count with system version on the switch brew site.
download the system version matching the system from *Cough* in the form of a system update...

Use memloader to mount the switch with hacdiskmount,
Use choidujour.exe with command line and create a nand rebuild to be restored to the switch from hacdiskmount with your biskeys... From the Hacdiskmount guide
Once you used hacdiskmount to transfer the files,Also place the fs kip on the root of your sd card and the hekate.INI into your sd card, this will fix Cust data and you may have to run briccmii to unbriic and rebriicc (enable disable autorcm, so remember to use jig if you disable it and boot)You can renable after you get backup and running...


Backup
https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/

Fusecount
https://switchbrew.org/wiki/Fuses

Applications and files
https://switchtools.sshnuke.net/

Hacdiskmount guide
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/


official update = fuse burn, and you should have ban if you booted sysnand...
He has not Burned fuses, he bypassed the fuse check with hekate.. any update done with hekate bypasses fuse check
 
Last edited by Canna,
I use SX but Atmosphere is way better on creport and stuff. Reinx is ams made by script kiddies

Wrong again. The only thing reinx uses of atmo aside from sept for 7.x booting which was agreed upon by scires and rei, is it uses a version of the sysmodules.

You can goto the reinx and atmosphere githubs and compare it yourself.
 
Last edited by Adran_Marit,
  • Like
Reactions: Philliyxx
Yes it can..

do you have a backup ?

Store the backup some were safe.
Get the fuse count with briccmii payload..
Once you compare the fuse count with system version on the switch brew site.
download the system version matching the system from *Cough* in the form of a system update...

Use memloader to mount the switch with hacdiskmount,
Use choidujour.exe with command line and create a nand rebuild to be restored to the switch from hacdiskmount with your biskeys... From the Hacdiskmount guide
Once you used hacdiskmount to transfer the files,Also place the fs kip on the root of your sd card and the hekate.INI into your sd card, this will fix Cust data and you may have to run briccmii to unbriic and rebriicc (enable disable autorcm, so remember to use jig if you disable it and boot)You can renable after you get backup and running...

Essentially rebuild my nand and try and update again? Will try. I already ave a previous 5.1 generated nand which I downgraded manually successfully with, I've done that guide almost 6 times now.

You know I did not mention on here that I mounted my system partition with hackdisk mount deleted all but the 1 file you are supposed to keep. Rebooted and this forced my 5.1 to initialize. Fresh format my SD card fat32. Then I made sure I could boot reinx and atmosphere fine and only put 7.0.1 fw files and choidujournx. Upgraded chose exfat update and guess what, switch bricked never could get past black screen after Nintendo logo. Think it has something to do with my boot 0 and 1?
 
Essentially rebuild my nand and try and update again? Will try. I already ave a previous 5.1 generated nand which I downgraded manually successfully with, I've done that guide almost 6 times now.

You know I did not mention on here that I mounted my system partition with hackdisk mount deleted all but the 1 file you are supposed to keep. Rebooted and this forced my 5.1 to initialize. Fresh format my SD card fat32. Then I made sure I could boot reinx and atmosphere fine and only put 7.0.1 fw files and choidujournx. Upgraded chose exfat update and guess what, switch bricked never could get past black screen after Nintendo logo. Think it has something to do with my boot 0 and 1?
Use the method i mentioned choose the system version you want , use choidujour .exe with command line

place the fskip on root of sd card and hekate ini onto bootloader folder on sd card

those two files are in the outputted choidujour folder..

as long as you have a backup of prodinfo and prodinfo f and your biskeys you can recover from any nand brick except hardware failure to any fw version
 
Last edited by Canna,
Script kitties is a harsh term coming from someone who spent 40 dollars for a useless piece of garbage that can barely Run something as simple as homebrew.
I have to agree that most homebrew crash through the SX menu. I just use this shit for emunand. Again, take the jig and reboot, am I safe? With emunand yes. I wait, and I promise I switch if other features become opensource
 
Use the moethod i mentioned choose the system version you want , use choidujour .exe with command line

place the fskip on root of sd card and hekate ini onto bootloader folder on sd card

those two files are in the outputted choidujour folder..

as long as you have a backup of prodinfo and prodinfo f and your biskeys you can recover from any nand brick except hardware failure to any fw version


You are explaining to me how to downgrade, thank you for that. I am trying to get to 6.2 or above from a lower firmware, you cant do that with choidujour yet. Still...I will try to downgrade manually to 5.1 and then upgrade to 6.2 with choidujournx and let you know what happens, even though I have essentially done so.
 
You are explaining to me how to downgrade, thank you for that. I am trying to get to 6.2 or above from a lower firmware, you cant do that with choidujour yet. Still...I will try to downgrade manually to 5.1 and then upgrade to 6.2 with choidujournx and let you know what happens, even though I have essentially done so.

Incorrect you can downgrade and upgrade with choidujour.exe
 
  • Like
Reactions: gizmomelb
I have to agree that most homebrew crash through the SX menu. I just use this shit for emunand. Again, take the jig and reboot, am I safe? With emunand yes. I wait, and I promise I switch if other features become opensource

press the R button when launching homebrew under SX OS and it'll launch with full memory access and not crash. you need the homebrew (is it nro or nsp, no time to check) on your SD card as well.

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

You are explaining to me how to downgrade, thank you for that. I am trying to get to 6.2 or above from a lower firmware, you cant do that with choidujour yet. Still...I will try to downgrade manually to 5.1 and then upgrade to 6.2 with choidujournx and let you know what happens, even though I have essentially done so.

yeah you can.. I did a fresh SX OS emuNAND install on my firmware 3.0.2 switch, then booted into SX OS emuNAND and updated straight to 6.2 with choidujourNX.. all working with no issues.

edit: that might be the issue.. you keep mention base choidujour, try the updated choidujournx.. in a hurry to work sorry.
 
Last edited by gizmomelb,
press the R button when launching homebrew under SX OS and it'll launch with full memory access and not crash. you need the homebrew (is it nro or nsp, no time to check) on your SD card as well.

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



yeah you can.. I did a fresh SX OS emuNAND install on my firmware 3.0.2 switch, then booted into SX OS emuNAND and updated straight to 6.2 with choidujourNX.. all working with no issues.

edit: that might be the issue.. you keep mention base choidujour, try the updated choidujournx.. in a hurry to work sorry.
Base choidujour is command line based.for pc/linux
Choidujournx is switch based with gui

Either or either ( 1 or the other) or ether one will do the job :P
 
  • Like
Reactions: gizmomelb
yeah you can.. I did a fresh SX OS emuNAND install on my firmware 3.0.2 switch, then booted into SX OS emuNAND and updated straight to 6.2 with choidujourNX.. all working with no issues.

edit: that might be the issue.. you keep mention base choidujour, try the updated choidujournx.. in a hurry to work sorry.
Because as per the first post of the thread (which I can't tell if everyone is skipping past after someone decided to bump this thread on Tuesday), OP could not update with ChoiDujourNX because the firmware(s) he wants to be on, 6.2-7.X, results in a black screen with both ReiNX and Atmosphere.
 
  • Like
Reactions: Philliyxx
Followed all instructions to downgrade to 5.1 manually. Got to the end to load FSXXX.kip(in my case 5.1). switch hangs and bricks on nintendo switch logo. If i try to boot atmosphere I get
Fatal error: [NXBOOT]: Couldn;t parse boot0: not enough space! Press power to reboot. When I try and push the reinx bin I get a real quick flash of a black screen,boot splash, then switch kicks back into rcm mode.
 
Base choidujour is command line based.for pc/linux
Choidujournx is switch based with gui

Either or either ( 1 or the other) or ether one will do the job :P

I thought choidujour couldn't cope with installing 7.x & only Choidujournx works now.

I'd probably restore the nand that works then try doing a reset factory settings in recovery mode & then try running atmosphere 0.8.6.



Then try choidujournx to install 7.x
 
Last edited by smf,
  • Like
Reactions: gizmomelb
Followed all instructions to downgrade to 5.1 manually. Got to the end to load FSXXX.kip(in my case 5.1). switch hangs and bricks on nintendo switch logo. If i try to boot atmosphere I get
Fatal error: [NXBOOT]: Couldn;t parse boot0: not enough space! Press power to reboot. When I try and push the reinx bin I get a real quick flash of a black screen,boot splash, then switch kicks back into rcm mode.
DID YOU USE THE BOOT 0 AND BOOT 1 FILES GIVEN TO YOU FROM THE CHOIDUJOUR OUTPUT FOLDER ?
 

Site & Scene News

Popular threads in this forum