Hacking Updated to 6.2 Now I cannot boot CFW or OFW

Philliyxx · Jan 10, 2019

Any have this issue?

I was on 5.1 RajNX for the last 2 months. SD is EXFAT.

I jumped to ReiNX 2.0 today. Everything fine booted up, etc.

Loaded ChoidujourNX and upgraded to 6.2 FW as I have done before from 4-5.1. Chose exfat as an option as well as RCM, which I did the last time.

Now when I try to boot Atmosphere or ReiNX or even OFW switch freezes at black screen after the initial splash screen. I can push the payloads from hekate but switch never gets to boot up.

Anyone experience this? I have reformated SD card and same thing happens.

*FIXED AND BOOTED CFW*

To sum up the entire process I did to get my switch to boot back up on fw 5.1 after upgrading to 6.2 and bricking.

Restored my original 4.1 nand backup(still could not boot up, fuses show 5 burned)
Followed this guide https://gbatemp.net/threads/how-to-...unofficially-without-burning-any-fuses.50746/

First attempt after finishing guide, was not able to boot; tried a second time using total commander instead of file explorer to transfer SYSTEM files switches EMMC(still was unable to boot)

3. Did a GPT restore using tool from https://switchtools.sshnuke.net/
4. Mounted and formatted SYSTEM and USER partitions with GUItool 16k cluster size.
5. Tried the Chodujour manual guide again, still unable to boot.
6. Loaded ReiNX 2.0 on SD card, sent payload from hekate 4.6(did not boot)
7. Sent ReiNX2.0 payload straight from tegrasmash (did not boot); tried 2 more times and finally booted past spash screen!!!

jysinn · Jan 10, 2019

Mine does it time to time..

What you have to do is when it hangs on the back screen plug the witch back to what your using to send the payload and load it up again. For some reason the second try boots it.

I think it boots back to RCM mode after try to launch.

Philliyxx · Jan 10, 2019

jysinn said:
Mine does it time to time..

What you have to do is when it hangs on the back screen plug the witch back to what your using to send the payload and load it up again. For some reason the second try boots it.

I think it boots back to RCM mode after try to launch.

Hmm not working, once it hits the black screen rcm is no longer detected.

spuderump · Jan 10, 2019

Got yourself a brick then.

Philliyxx · Jan 10, 2019

spuderump said:
Got yourself a brick then.

damn was afraid of that. I have a nand back up will restoring possibly fix?

spuderump · Jan 10, 2019

Worth a try I guess.

Philliyxx · Jan 10, 2019

I have 5 burnt fuses and my original NAND backup was from 4.1, so I should be good to downgrade, but before I do I want to exhaust all options

Kubas_inko · Jan 10, 2019

Philliyxx said:
I have 5 burnt fuses and my original NAND backup was from 4.1, so I should be good to downgrade, but before I do I want to exhaust all options

Your only options (afaik):
1. Restore your NAND.
2. Recreate your NAND.

Deobulakenyo · Jan 10, 2019

Why do this happen? This is not the first time i read about this and the reason why i am afraid to update.

ucef · Jan 10, 2019

Deobulakenyo said:
Why do this happen? This is not the first time i read about this and the reason why i am afraid to update.

Autorcm brick the switch on purpose,corrupting some bits on the BOOT0 so time to time you gonna have some trouble!some people do some don't !
(in my opinion)

Kubas_inko · Jan 10, 2019

ucef said:
Autorcm brick the switch on purpose,corrupting some bits on the BOOT0 so time to time you gonna have some trouble!some people do some don't !
(in my opinion)

100% not caused by Autorcm.

ucef · Jan 10, 2019

did you try to boot on OFW without the sd card?

N3wbs · Jan 10, 2019

Why you not using emunand on your sd?
Restore 4.1
Buy a sx os .. load the payload ..

Make a emunand on your sd cart, after run the emunand .. keep your ofw to 4.1 and update emunand on the sd to 6.1 with choidujour .. (exfat format)
ps : before updating emunand you can put the original firmware white theme and cfw emunand in dark theme . (That just a tip to know whats you loaded .. ofw or cfw .. and update emunand .

If a day you brick the emunand .. you can make a other one .. and with this .. you can have a CLEAN OFW(dont use hack on them) (if you want wait for a coldboot or update to playing online without get banned) and use emunand on sd to run homebrew and no legit games .

That just a tip that whats im using atm No problem for now.

That just a idea.. other cfw was good too that just a good option to use sx os .. because you can run xci backup without need to install them from hhd plugged in dock and you have a emunand option for the sd cart .. the emunand is not installed on your ofw firmware.

lieder1987 · Jan 10, 2019

I had the same issue last night (upgraded to 6.2 using ChoidujourNX then I only got black screen after SXOS splash screen), was able to pull the SD card, upgrade through official firmware and now back in business.

Deobulakenyo · Jan 10, 2019

lieder1987 said:
I had the same issue last night (upgraded to 6.2 using ChoidujourNX then I only got black screen after SXOS splash screen), was able to pull the SD card, upgrade through official firmware and now back in business.

What do you mean you were able to pull the sd card? And what official fw? Isn't the fw used for choinx official too?

lonestarrisk · Jan 10, 2019

I had the same issue but with sx os. Updated with choid from 4 to 6.2. For me I had to charge up the switch and change the payload file after putting the exfat update on the console.

lieder1987 · Jan 10, 2019

Deobulakenyo said:
What do you mean you were able to pull the sd card? And what official fw? Isn't the fw used for choinx official too?

I took the SD out, and then I was able to boot directly into the official firmware. I then was able to "upgrade" again after just doing 6.2.0 using choinx.

Moquedami · Jan 10, 2019

I had a similar issue last night.
I have SX os and never used emunand whatsoever.
I updated to 6.2 OFW online.
Next thing, the console won´t boot to CFW and shows error 2011-0301
OFW boots just fine.
I try a second sd card and boots OFW and CFW fine.
My guess is that somehow the first SD got corrupted when updating.
I format the SD card and copy over the files from the second one, and it starts to work all right again.

mitcha · Jan 10, 2019

was having the same issue as OP , i was on 5.1 cfw rajnx , then i upgrade to 6.2 atmosphere , what happen is it can't boot at all even with hekate.
i start from scratch formated the sd card then put kosmo and atmosphere files , launch hekate 4.6 and its ok for me , i was doing the same thing last night with black screen boot.
so start a fresh instalation with the minimum files, hope it helps.

Philliyxx · Jan 10, 2019

I will try to boot ofw with SD card out. I tried with it in and it froze on Nintendo Logo.

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

mitcha said:
was having the same issue as OP , i was on 5.1 cfw rajnx , then i upgrade to 6.2 atmosphere , what happen is it can't boot at all even with hekate.
i start from scratch formated the sd card then put kosmo and atmosphere files , launch hekate 4.6 and its ok for me , i was doing the same thing last night with black screen boot.
so start a fresh instalation with the minimum files, hope it helps.

Hmm I will try a second SD format and fresh install. Should I try fat32 instead of exfat?

Hacking Updated to 6.2 Now I cannot boot CFW or OFW

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

"Something funny goes here."

Well-Known Member

Well-Known Member

"Something funny goes here."

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

مجاهد صنديد مقاتل عنيد

Well-Known Member

Similar threads

Popular threads in this forum