Hacking Question Black screen after CFW logos after updating Firmware/Atmosphere

[stefko13]

Okay, so this has me a little worried.

I was on 8.0.1 and Atmosphere 0.8.4 (not sure about the latter). I wanted to update to 9.0.1. and Atmosphere 0.9.4. So here's what i did:

1. Downloaded a new zip package from sdsetup
2. Pasted the contents onto my MicroSD card
3. Booted the Switch into CFW, everything worked fine
4. Used ChoiDuJourNX to update to 9.0.1 + enabled AutoRCM
5. Selected "Shutdown Now"
6. Tried turning my Switch on with the RCM jig and TegraRCMGUI

Now my Switch shows me the Atmosphere logos and after that just a black screen. I can only guess where i went wrong. My SDCard was formatted as Fat32 but after googling, someone said one should still select the ExFat option when installing the new firmware with ChoiDuJourNX, so i did that. Or maybe i fucked up by inserting a jig, even though AutoRCM was enabled? I honestly don't know.

I can boot into Hekate (got the newest version of it) but the Touchscreen doesn't work at all. Currently i'm in the process of transferring the contents of my SDCard over to my PC after which i want to format my SDCard, get a new clean Atmosphere package and put that onto the newly formatted SDCard (again going to choose Fat32).

So, does somebody know what i did wrong? I hope i didn't screw up completely.

 

[smf]

So, does somebody know what i did wrong? I hope i didn't screw up completely.

Do you use themes? Or any other system modules that aren't included by default?

It's been a while since I used hekate, does it even use the touchscreen?

 

[stefko13]

I never used any custom themes. I'm sorry, i don't know what you mean by system modules and google doesn't exactly help me :/. I selected the Default Kosmos Package on SDSetup to do this.

Side note: Some of the research i'm doing is pointing towards problems with Fat32/exFat. Maybe choosing (9.0.1. exfat) in ChoiDuJourNX was the wrong choice after all. Not that i want to concentrate on that specifically, i'm just trying to help myself out, since i'm already sorry for adding yet another thread asking for help. I've already always been as cautious as i could when handling CFW with my Switch.

 

[stefko13]

Oh and yes, Hekate does use the touchscreen nowadays.

 

[SedRick_M89]

Guys, I've just accidentally allowed my switch to perform a system update whilst on CFW...
I can't boot past Hekate anymore..

How can i fix this?

Please please

 

[stefko13]

Phew, i fixed my issue. I don't know how exactly i did it but here is what i did:

1. Backed up my SD Card (as i said in my first post)
2. Formatted it in Fat32 again with Guiformat
3. Put all files from the newst SDSetup Default package on my SDCard
4. Booted into CFW with Fusee Primary

Now, this is weird though: I tried it with Hekate first, the newest version. It booted up with the old text interface. The default Atmosphere zip (just the pure Atmosphere CFW, not SDSetup, as i read somewhere a basic Atmosphere package might work best) was missing some files ("main configuration not found"). So i went for the SDSetup. Now this time it booted into the graphical Hekate menu. I used the same Hekate file both of those times.
Then i was still stuck with a non-functioning Hekate. I used Fusee Primary to boot and it worked just fine. But it would still be nice to know why Hekate is acting up because i might want to try EmuNAND at some point...that point being where i feel i finally understand how to do it.

 

[SedRick_M89]

Am i the only one that has updated the system firmware whilst on atmosphere??

i am currently backing up my entire Switch SD preparing for a NAND restore as i cant think of another way around it, i have never done a NAND restore before and googling my issue isn't much help..

So if anyone else has experienced the same thing, or if anyone knows a way to regain the life of the switch without restarting from scratch,
Please let me know

Thanks in advance

 

[stefko13]

Am i the only one that has updated the system firmware whilst on atmosphere??

i am currently backing up my entire Switch SD preparing for a NAND restore as i cant think of another way around it, i have never done a NAND restore before and googling my issue isn't much help..

So if anyone else has experienced the same thing, or if anyone knows a way to regain the life of the switch without restarting from scratch,
Please let me know

Thanks in advance

This thread is about my pretty niche issue, so idk if you'll get an answer here. I'd suggest, open a new thread man, i'm sure somebody will be able to help you. Don't rely on my opinion but a Nand Backup sounds like the right way to go in my opinion. I mean, your Atmosphere version probably doesn't support your current firmware version and with a Nand Backup you'd revert back to an older firmware. Sounds like the right idea to me. But i would definitely open a new thread and wait for smarter people to help you out! Good luck man, don't worry!

 

[nifoc2099]

So if anyone else has experienced the same thing, or if anyone knows a way to regain the life of the switch without restarting from scratch,
Please let me know

Thanks in advance

You are not providing sufficient information.Basically is your hekate working or not? Have you done a NAND Backup before your "accident" update.