Hacking RELEASE [Official] ReiNX thread [DEAD]

[Deleted User]

Firmware 6.1.0 has just been released by Nintendo.

I cant boot into Reinx on 6.1.0

 

[Kilim]

I cant boot into Reinx on 6.1.0

autoRCM was disabled on update, re-enable it with the jig

 

[Deleted User]

autoRCM was disabled on update, re-enable it with the jig

Its enabled and I can boot other cfws - Cant load ReiNX newest build and nightly get package error at orange text screen "Package2 Magic Invalid"

Finally got ReiNX to load through pc. Keep getting error trying to boot from trinket. Wonder if new Trinket files are needed. Hekate and Rajnx would not load my installed nsps on 6.10.

 

[MikeB2018]

I cant boot into Reinx on 6.1.0

Neither can I. It boots RCM. I can inject payload, I can see the ReiNX splash screen for halloween, I can see Nintendo Switch logo. But right then, it gives me an error and tells me to press power button to Shut Down the console.

I can start RajNX, and open/play .nsp copies, normally. But I'd really like to continue using ReiNX. (IMO the first and only free CFW. Really supporting Rei's development team).

Can anyone help me, plz?

PD. AutoRCM is enabled.

 

[Deleted User]

Neither can I. It boots RCM. I can inject payload, I can see the ReiNX splash screen for halloween, I can see Nintendo Switch logo. But right then, it gives me an error and tells me to press power button to Shut Down the console.

I can start RajNX, and open/play .nsp copies, normally. But I'd really like to continue using ReiNX. (IMO the first and only free CFW. Really supporting Rei's development team).

Can anyone help me, plz?

PD. AutoRCM is enabled.

For me:

RajNX loads and hombrew works but 99% of my nsps wont load 6.1
ReiNX loads with Tegra and works with 6.1 and all my nsps load - With Trinket CFW will not load stuck on package2 patching OS
Hekate - I finally got it to load all my nsps. I had to re-do sd files for cfw only and re-enable cfw auto boot then all nsps worked again

 

[texasrngrnorris]

After updating to 6.1.0, using the latest version of Rekado for android to paunch ReiNX.bin, the splash screen appears, goes black, and then the nintendo logo appears. After this, it boots into the FW that I thought was CFW. At this point, any games that I installed with tinfoil work, as well as the retroarch NSP. However, clicking on the album folder does not bring me to homebrew. Any suggestions?

 

[Draxzelex]

After updating to 6.1.0, using the latest version of Rekado for android to paunch ReiNX.bin, the splash screen appears, goes black, and then the nintendo logo appears. After this, it boots into the FW that I thought was CFW. At this point, any games that I installed with tinfoil work, as well as the retroarch NSP. However, clicking on the album folder does not bring me to homebrew. Any suggestions?

If you updated to 6.1 officially and are currently using an exFAT formatted SD card, the console no longer recognizes the SD card because the firmware doesn't support exFAT. Either accept the SDXC prompt to get exFAT on 6.1 or reformat your SD card to FAT32.

 

[texasrngrnorris]

If you updated to 6.1 officially and are currently using an exFAT formatted SD card, the console no longer recognizes the SD card because the firmware doesn't support exFAT. Either accept the SDXC prompt to get exFAT on 6.1 or reformat your SD card to FAT32.

It appears as though it does support the SD card, as I can load games that are stored entirely on the card, as well as retroarch. I also do not get a prompt for exFAT on 6.1.0. I tried deleting the album folder inside of the Nintendo folder on the SD card, but that did not work.

 

[Draxzelex]

It appears as though it does support the SD card, as I can load games that are stored entirely on the card, as well as retroarch. I also do not get a prompt for exFAT on 6.1.0. I tried deleting the album folder inside of the Nintendo folder on the SD card, but that did not work.

Check if you have a folder ending in 100D under /ReiNX/titles. If not, redownload them from the guide.

 

[sekuza009]

Hey there, if had a weird issue ever since enabling AutoRCM on my Switch. Basically what happens is when I turn off my console it kinda sits there and doesn't turn off. If I remove a Joycon and press a button they like connect and vibrate. I have to hold the power button 12 seconds to have it fully turn off and then then the console will turn on in RCM mode and have no issues. Do you guys know how to fix this?

 

[Draxzelex]

Hey there, if had a weird issue ever since enabling AutoRCM on my Switch. Basically what happens is when I turn off my console it kinda sits there and doesn't turn off. If I remove a Joycon and press a button they like connect and vibrate. I have to hold the power button 12 seconds to have it fully turn off and then then the console will turn on in RCM mode and have no issues. Do you guys know how to fix this?

That's expected. A console with AutoRCM installed does not fully turn off when shutdown from Horizon. Instead, it reboots into RCM. In order to properly turn off a console with AutoRCM installed, you must power it down from RCM. Examples include Hekate's Power Off function or a manual shutdown (holding power for 12 seconds).

 

[sekuza009]

That's expected. A console with AutoRCM installed does not fully turn off when shutdown from Horizon. Instead, it reboots into RCM. In order to properly turn off a console with AutoRCM installed, you must power it down from RCM. Examples include Hekate's Power Off function or a manual shutdown (holding power for 12 seconds).

Hmm, well the thing is when I plug it in, it shows up as Nintendo Switch and not the RCM mode, so it won't actually go into and let the payload go until I fully power off and turn it back on. Unless I'm misunderstanding.

 

[Reisyukaku]

Hmm, well the thing is when I plug it in, it shows up as Nintendo Switch and not the RCM mode, so it won't actually go into and let the payload go until I fully power off and turn it back on. Unless I'm misunderstanding.

AutoRCM is just writing to nand to corrupt it forcing the console into RCM mode (recovery).. but when you update what do you think happens to the nand? its written to with the new firmware lol... Not sure why people are suddenly bringing this up since it's been known since i first implemented AutoRCM in hekate. x3
Simply use jig to enter cfw and re-enable autorcm.. For those wanting to preserve fuses on update, simply have a jig in place the buttons ready to be pressed to enter rcm mode after the update restarts the console..

 

[sekuza009]

AutoRCM is just writing to nand to corrupt it forcing the console into RCM mode (recovery).. but when you update what do you think happens to the nand? its written to with the new firmware lol... Not sure why people are suddenly bringing this up since it's been known since i first implemented AutoRCM in hekate. x3
Simply use jig to enter cfw and re-enable autorcm.. For those wanting to preserve fuses on update, simply have a jig in place the buttons ready to be pressed to enter rcm mode after the update restarts the console..

Nyeh, I'm a noob Rei. I re-enabled it but that same thing is happening. I could show you if I'm not making sense though.

 

[Reisyukaku]

Nyeh, I'm a noob Rei. I re-enabled it but that same thing is happening. I could show you if I'm not making sense though.

Re-enbled with the toolkit? because it'll tell you if its enabled.. i mean i accidentally updated to 6.1 because i didnt know it was out and i re-enbled rcm fine.

 

[sekuza009]

Re-enbled with the toolkit? because it'll tell you if its enabled.. i mean i accidentally updated to 6.1 because i didnt know it was out and i re-enbled rcm fine.

Yeah, in the Toolkit. It's enabled. I can show you a video if that'd be more helpful.

 

[sekuza009]

Yeah this is what it's doing: https://photos.app.goo.gl/hKJnHmkvAYMyWaow6 I also need to mention that sometimes it doesn't boot with the payload but I figure that's expected. Edit: accidentally linked the wrong video, put the new one here though.

 

[Reisyukaku]

Yeah this is what it's doing: https://photos.app.goo.gl/hKJnHmkvAYMyWaow6 I also need to mention that sometimes it doesn't boot with the payload but I figure that's expected. Edit: accidentally linked the wrong video, put the new one here though.

Well i see nothing wrong with autorcm.. just looks like for whatever reason the cfw hung.. i'd say try latest build/clean install.. too many people leave artifacts like fs.kip and other shit that break stuff because they just overwrite old files..

 

[sekuza009]

Yeah, for sure. I'll try that and see if it makes a difference. I did however notice it happening in OFW to a certain point too, but it seemed like it fixed itself. A clean install is for sure worth a shot though.

 

[Reisyukaku]

Yeah, for sure. I'll try that and see if it makes a difference. I did however notice it happening in OFW to a certain point too, but it seemed like it fixed itself. A clean install is for sure worth a shot though.

Well i was told OFW had sleep mode bug too where it doesnt come out of sleep mode.. so yea.. running hack patches on a hacky OS is fun x3