Hacking RELEASE [Official] ReiNX thread [DEAD]

[nycat]

With a clean NAND backup are impossible that it report 6.0 ReiNX

So in the scenario that the guide describes: Boot RCM payload that includes layered fs to launch homebrew menu from album.

I followed that process and got a *lot* of crashes on FW 2.1, so before I managed to take a full NAND backup, I ended up with a bunch of crash logs from the homebrew and whatever else.
Looking back now I realise that a payload like Hekate would have been more appropriate to dump a clean NAND, but the guide never included this for some reason.
What steps should I take to get these reports "cleaned" out, and what else would the homebrew menu have left behind before the backup took place?

 

[Draxzelex]

So in the scenario that the guide describes: Boot RCM payload that includes layered fs to launch homebrew menu from album.

I followed that process and got a *lot* of crashes on FW 2.1, so before I managed to take a full NAND backup, I ended up with a bunch of crash logs from the homebrew and whatever else.
Looking back now I realise that a payload like Hekate would have been more appropriate to dump a clean NAND, but the guide never included this for some reason.
What steps should I take to get these reports "cleaned" out, and what else would the homebrew menu have left behind before the backup took place?

Clearing error logs has been known to cause bans so the tool to do so has been removed from the public. There isn't really much of anything you can do at this point if you didn't make a NAND backup before hacking. While it would be useful for preventing a ban, linking Hekate in a ReiNX oriented guide would confuse users since its a different payload and would only be needed for that one step.

 

[nycat]

Clearing error logs has been known to cause bans so the tool to do so has been removed from the public. There isn't really much of anything you can do at this point if you didn't make a NAND backup before hacking. While it would be useful for preventing a ban, linking Hekate in a ReiNX oriented guide would confuse users since its a different payload and would only be needed for that one step.

Gotta admit, it's pretty unfortunate for a guide to be written that causes harmful changes to a console.
If users are willing to run random payload blobs from USB, I hardly think that it's confusing to use an objectively superior method (crash stability, NAND authenticity) to do so.

On the flip side then, how viable is it to reconstruct an untouched NAND using files dumped from a console that has never entered horizon/never run homebrew?
As far as I can tell outside of the console specific info, if the various filesystems were byte-for-byte identical to a console that has never been used, would it not be comparable to a factory reset? Well, better off asking reverse engineers I guess.

On that note, how does a factory reset affect crash reports and such? Do we have that info?

Cheers.

EDIT:
Better yet, is there any way to audit the crash report logs in a meaningful way?
I'd happily delete the unofficial entries manually, assuming that there's no counter or similar that would track tampering. Again, really something that would require dev input.

 

[Draxzelex]

Gotta admit, it's pretty unfortunate for a guide to be written that causes harmful changes to a console.
If users are willing to run random payload blobs from USB, I hardly think that it's confusing to use an objectively superior method (crash stability, NAND authenticity) to do so.

On the flip side then, how viable is it to reconstruct an untouched NAND using files dumped from a console that has never entered horizon/never run homebrew?
As far as I can tell outside of the console specific info, if the various filesystems were byte-for-byte identical to a console that has never been used, would it not be comparable to a factory reset? Well, better off asking reverse engineers I guess.

On that note, how does a factory reset affect crash reports and such? Do we have that info?

Cheers.

EDIT:
Better yet, is there any way to audit the crash report logs in a meaningful way?
I'd happily delete the unofficial entries manually, assuming that there's no counter or similar that would track tampering. Again, really something that would require dev input.

Factory resets do not clear the error logs hence why clearing them would flag you for a ban; because clearing them is impossible without hacking the console.

And the tool to remove error logs was replaced with one that instead redirects them to the SD card since this is much safer than manually deleting them. Known as creport, it is presently not bundled with ReiNX however it can be found in RajNX and tomGER's SD files.

 

[nycat]

Factory resets do not clear the error logs hence why clearing them would flag you for a ban; because clearing them is impossible without hacking the console.

And the tool to remove error logs was replaced with one that instead redirects them to the SD card since this is much safer than manually deleting them. Known as creport, it is presently not bundled with ReiNX however it can be found in RajNX and tomGER's SD files.

Yes, you've made it quite clear that removing *all* of them is a bad idea. Hence why I suggested removing them individually. Which would be totally safe unless there was some algorithm behind them that would track how many exist, or some other special information.

Reading over: switchbrew org/wiki/Creport
Apparently there's no technically sound checks in place to prevent removing specific entries, well at least not until v3.0+? (Specifically v5.0)
According to: twitter com/SciresM/status/1011321806207107072

Well, there's nothing for it really. I'll find out when I try taking it online, worst case scenario it gets banned, if it can't otherwise go online then there's really no difference.

 

[Dave_Chad]

I'm still confused as to if I'm the only one with sleep mode of death on latest release and on nightlies.

Also is it just ReinX or present in Atmos too.

Sent from my COR-L29 using Tapatalk

 

[arianadark]

I'm still confused as to if I'm the only one with sleep mode of death on latest release and on nightlies.

Also is it just ReinX or present in Atmos too.

Sent from my COR-L29 using Tapatalk

sleep mode works for me, delete your homebrew files you have installed and put a fresh copy of the files.

 

[Chocola]

how do i check this? same problem here, but i can not remember, if i used any bootloader patches...

If you use ReiNX.bin to launch the CFW then you aren't using any previous patch or custom bootrom, but if you launch ReiNX from Hekate, it's possible that you have it configured on the config file of bootroom folder.

If you use Hekate, update it to 4.2 too, the problem was solved on last Hekate and ReiNX builds.

 

[deadlycfx]

I just bought a switch with firmware 4.10 and I also confirm that the hardware date is before July 2018. On the installation guide, there is a part (listed below) about the SDcard that I have a question.

• Please note, if you do decide to use exFAT, your Switch must download an update to utilize this, which means it must be on the latest firmware. As far as installing the update, all you have to do is insert an exFAT Micro SD Card into your Switch while it's on and it will prompt you to download an update. Easy stuff.

Does this mean that I will need to connect the internet and accept the latest firmware (6.0) to be able to format the SDcard to exFAT? I would then need to install ReiNX nightlies, rather than the lastest stable release?

 

[Draxzelex]

I just bought a switch with firmware 4.10 and I also confirm that the hardware date is before July 2018. On the installation guide, there is a part (listed below) about the SDcard that I have a question.

• Please note, if you do decide to use exFAT, your Switch must download an update to utilize this, which means it must be on the latest firmware. As far as installing the update, all you have to do is insert an exFAT Micro SD Card into your Switch while it's on and it will prompt you to download an update. Easy stuff.

Does this mean that I will need to connect the internet and accept the latest firmware (6.0) to be able to format the SDcard to exFAT? I would then need to install ReiNX nightlies, rather than the lastest stable release?

That is one option. You can also install the exFAT patch on any firmware except 1.0 with the homebrew app, ChoiDujourNX. It goes without saying that the SD card must be FAT32 in order to install the exFAT patch with ChoiDujourNX.

 

[deadlycfx]

Draxzelex,

So basically finish installing ReiNX with a FAT32 SDcard, then use ChoidujourNX to install the patch, then reformat the SDcard to exFAT and copy all necessary files back to the SDcard? Thanks.

 

[Draxzelex]

Draxzelex,

So basically finish installing ReiNX with a FAT32 SDcard, then use ChoidujourNX to install the patch, then reformat the SDcard to exFAT and copy all necessary files back to the SDcard? Thanks.

First, you cannot install ReiNX; the CFW is temporarily applied every time you send the ReiNX payload. ReiNX is just a collection of files on the SD card meaning it is not written to the Switch permanently.

Secondly, if you are able to successfully launch ReiNX, then you may use ChoiDujourNX to install the patch and reformat the SD card to exFAT.

 

[deadlycfx]

Draxzelex,

Got it. Thanks for your help.

 

[Chocola]

Draxzelex,

Got it. Thanks for your help.

Use FAT32 SD card for the first steps, the first step it's make a full NAND backup before runing any mod with hekate, after the full backup, then you can proceed.

Honestly, I don't recomend you to go to v6.0, the online features aren't working on CFW (always end on console ban) and for now no game require this versión, I don't recomend you connect your console to Internet, just leave empty the wireless configuration and enable air plane mode to be more safe.

I recomend the v5.1.0 for now, it cover all game required versions and include the exFAT support, you need a game cartige image with this update or the update itself, I don't able to provide you these files because are licensed by N.

When you have the update ready, then you should prepare ReiNX as is explained on the guide, then use ChoiDujourNX to update your Switch without burning fuses (Let you roolback to the v4.10 without problems, on the update process, you gona see a question with two options, select 5.1.0 (exFAT) and this add exFAT support with the update automatically.

When you are on 5.1.0 with exFAT support, copy your current SD content to a temporary folder of your PC, format the SD card to exFAT and then copy again the files to the SD.

 

[teaw]

error package 2 magic invalid

 

[Chocola]

error package 2 magic invalid

Bricked Switch, restore the clean NAND backup before do any more actions

 

[Powerful]

what’s left for ReiNX to be fully compatible with FW 6.0?

 

[Chocola]

what’s left for ReiNX to be fully compatible with FW 6.0?

It's compatible, but not recomended, it's a very recent version and some new things are pending of discover for now

 

[Deathscreton]

Is exFAT still broken or has a fix been implemented yet? Don't wanna nuke my SD card. :C

 

[Chocola]

Is exFAT still broken or has a fix been implemented yet? Don't wanna nuke my SD card. :C

exFAT working, but the exFAT driver of homebrew have a bug that can corrupt your SD filesystem, in my case 0 problems and I use exFAT like 1 month