Hacking Question Updated switch to 8.1.0. Now I cant boot

[Starkgod]

I've been out of the loop for a bit. But I'm certain I updated like normal. I was previously on 7.1 and needed to update to play a certain title.

Downloaded the update files from the usual place and fired up Choi. Process went as usual. Heres my setup.

128gb micro Sd. formatted to exfat.
Latest version of ReiNX
AutoRCM enabled.
TegraRCM to inject hekate 5.0.1 (Never bothered to fix what always worked)

Switch displays sept splash, then reinx splash, then the nintendo switch logo, then crashes.

Any ideas? I may have missed something.

I have a nand dump from pre cfw if anything.

 

[tglaria]

I has a problem with 8.1.0 not booting after upgrading with ChoiDuJour.
I uodated hekate to 5.0.2 I think and it worked again.

 

[Starkgod]

I has a problem with 8.1.0 not booting after upgrading with ChoiDuJour.
I uodated hekate to 5.0.2 I think and it worked again.

Tried this. Injected via tegra on pc. Got a menu that seems to requie a payload on sd to launch. How would I do this? Just want to be sure.

 

[Starkgod]

necessary bump.

Still stuck here.

 

[Nastas95]

Did you have a custom theme?

 

[Starkgod]

Did you have a custom theme?

No custom theme at all

 

[Nastas95]

Did you try a clean installation of ReiNX/Atmosphere?

 

[Starkgod]

Did you try a clean installation of ReiNX/Atmosphere?

Yeah. I updated all the files after the initial crash happened. Should be noted that the crash screen notes that my firmware is on 8.1. So perhaps it isnt the firmware that is the issue? I'm not sure.

 

[Nastas95]

uhm... OFW boots fine?

 

[Starkgod]

uhm... OFW boots fine?

Loading into hekate 5.2 via the payload gives me the option to reboot into OFW. Doing so puts me back into RCM on a black screen,

 

[The Real Jdbye]

Tried this. Injected via tegra on pc. Got a menu that seems to requie a payload on sd to launch. How would I do this? Just want to be sure.

You need to update the SD files for Hekate as well. They're in the release archive.

Loading into hekate 5.2 via the payload gives me the option to reboot into OFW. Doing so puts me back into RCM on a black screen,

Rebooting into OFW is still loading through Hekate with some patches AFAIK (at least disabling fuse checks), the only way to get true OFW is to disable AutoRCM as there isn't to my knowledge a payload that just boots vanilla OFW. I might be wrong on that though. But I'm positive that rebooting into OFW from Hekate actually loads OFW from Hekate, it's not true rebooting. I guess it has to be that way, otherwise it wouldn't work with AutoRCM.

 

[Starkgod]

You need to update the SD files for Hekate as well. They're in the release archive.

Rebooting into OFW is still loading through Hekate with some patches (at least disabling fuse checks), the only way to get true OFW is to disable AutoRCM as there isn't to my knowledge a payload that just boots vanilla OFW.

Tried this. Replaced the bootloader folder on SD with the one included in the hekate zip. In menu both the 'launch' and 'more configs' menus show that there is somehow no boot entries found.

 

[The Real Jdbye]

Tried this. Replaced the bootloader folder on SD with the one included in the hekate zip. In menu both the 'launch' and 'more configs' menus show that there is somehow no boot entries found.

Did you replace hekate_ipl.ini? I didn't think that was included in the zip, but that's where your boot entries are located.

Anyway, chances are low that something would be wrong with both Hekate's built in loader and Atmosphere's.
Sounds more like your firmware was somehow bricked during the update, assuming your Atmosphere files are at least somewhat recent. A lot of people have been posting recently about not being able to boot after a Choi update. You should update Atmosphere and Hekate first of all, but if all else fails, you may have to rebuild the NAND (SYS partition and boot0/boot1 is good enough, don't mess with USER), there's a guide on that here: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

 

[Starkgod]

Did you replace hekate_ipl.ini? I didn't think that was included in the zip, but that's where your boot entries are located.

Anyway, chances are low that something would be wrong with both Hekate's built in loader and Atmosphere's.
Sounds more like your firmware was somehow bricked during the update, assuming your Atmosphere files are at least somewhat recent. A lot of people have been posting recently about not being able to boot after a Choi update. You should update Atmosphere and Hekate first of all, but if all else fails, you may have to rebuild the NAND (SYS partition and boot0/boot1 is good enough, don't mess with USER), there's a guide on that here: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

There was one on the root of my SD that I assume was old. As it didn't work when placed into bootloader. There doesnt seem to be a new one included in the zip off githubs latest version. Also, I am on ReiNX if that matters

 

[The Real Jdbye]

There was one on the root of my SD that I assume was old. As it didn't work when placed into bootloader. There doesnt seem to be a new one included in the zip off githubs latest version. Also, I am on ReiNX if that matters

It does go in bootloader. You should check the hekate_ipl.ini that is in bootloader and make sure the entries are there. Or did you accidentally delete it? Check your recycle bin.
In that case you need to be using the very latest version of ReiNX (released in June) as that's the only one that supports 8.1.
I would switch to Atmosphere if I were you, mainly because ReiNX takes way longer to be updated. Atmosphere gets an update within days, ReiNX still has not been updated for 9.0.0 which was released well over a month ago. Though you rarely need to be running the latest firmware if you're using an emuNAND, clearly more effort goes into maintaining Atmosphere (it likely has a bigger team behind it as well) and that is reason enough for me.

 

[Starkgod]

It does go in bootloader.
In that case you need to be using the very latest version of ReiNX (released in June) as that's the only one that supports 8.1.
I would switch to Atmosphere if I were you, mainly because ReiNX takes way longer to be updated. Atmosphere gets an update within days, ReiNX still has not been updated for 9.0.0 which was released well over a month ago.

I have only updated to 8.1, Reinx apparently supports this version. I also have the latest ReiNX.

Is there somewhere I can get the latest ini? It isn't in the hekate zip

 

[The Real Jdbye]

I have only updated to 8.1, Reinx apparently supports this version. I also have the latest ReiNX.

Is there somewhere I can get the latest ini? It isn't in the hekate zip

There is one on the Hekate GitHub that you can use as a template, but usually you would get it from your CFW package (many people use Kosmos but I don't think they have a config for ReiNX as it seems to be Atmosphere based)

Here is the template: https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini
It does not have an entry for ReiNX but you could just take the bottom entry for memloader and modify it to launch the ReiNX payload instead (and add a logo/boot screen if you like)
Apart from the bottom entry you should also keep the config section, everything else is optional, but does give you a config that would work for Atmosphere if you decide to switch
Or you could use Kosmos, but I decided to do it myself rather than use a package that I don't really understand how works or what exactly goes into.

Though you rarely need to be running the latest firmware if you're using an emuNAND, clearly more effort goes into maintaining Atmosphere (it likely has a bigger team behind it as well) and that is reason enough to make the switch for me. Most things are tested on it and not necessarily on ReiNX so it will always have better support as well.

 

[Starkgod]

There is one on the Hekate GitHub that you can use as a template, but usually you would get it from your CFW package (many people use Kosmos but I don't think they have a config for ReiNX as it seems to be Atmosphere based)

Here is the template: https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini
It does not have an entry for ReiNX but you could just take the bottom entry for memloader and modify it to launch the ReiNX payload instead (and add a logo/boot screen if you like)
Apart from the bottom entry you should also keep the config section, everything else is optional, but does give you a config that would work for Atmosphere if you decide to switch
Or you could use Kosmos, but I decided to do it myself rather than use a package that I don't really understand how works or what exactly goes into.

Though you rarely need to be running the latest firmware if you're using an emuNAND, clearly more effort goes into maintaining Atmosphere (it likely has a bigger team behind it as well) and that is reason enough to make the switch for me. Most things are tested on it and not necessarily on ReiNX so it will always have better support as well.

I'm not sure atmosphere supports nsp loading. Which is the main reason I need reinx. It seems like hekate 5.2 wont read any ini i put into the boot folder

 

[The Real Jdbye]

I'm not sure atmosphere supports nsp loading. Which is the main reason I need reinx. It seems like hekate 5.2 wont read any ini i put into the boot folder

Of course it does. You just need the patches from https://github.com/Joonie86/hekate/releases
They need to be updated every time there's a new firmware but get updated quickly.
Hmm, are you still getting the Nyx theme and not the basic text based UI? If the theme is able to load, it's obviously able to read your SD, so I don't know what would be wrong in that case, but if the theme isn't able to load the issue is pretty obvious.
Maybe it could be SD card corruption? Run a scan just to make sure.
Also, are you using ExFAT? That's more prone to corruption.

 

[Starkgod]

Of course it does. You just need the patches from https://github.com/Joonie86/hekate/releases
They need to be updated every time there's a new firmware but get updated quickly.
Hmm, are you still getting the Nyx theme and not the basic text based UI? If the theme is able to load, it's obviously able to read your SD, so I don't know what would be wrong in that case, but if the theme isn't able to load the issue is pretty obvious.
Maybe it could be SD card corruption? Run a scan just to make sure.
Also, are you using ExFAT? That's more prone to corruption.

Nyx theme loads fine. No SD corruption. I am mostly a layman. Is there a guide somewhere on what I would do with these patches exactly?