Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[Hayato213]

I think it's a bit difficult to find a donor and I've never deleted the prodinfo partition.

Atmosphere blanks it on boot (and it's not persistent).

If you use dns mitm with exosphere blanking it works fine on 17.0.0

If you were banned then no need to blank

 

[jmmc]

If you were banned then no need to blank

I know, I was testing for my cousin. Like I said, I've never used incognito or similar

 

[Deleted member 319555]

I have followed the https://rentry.org/SwitchHackingIsEasy guide, but I get the fussee version error, but I have copied the 1.6.1 fusee.bin to the payloads folder. I also get a Old Nyx, there will be dragons error, but I can click through that one. What am I doing wrong?

 

[impeeza]

I have followed the https://rentry.org/SwitchHackingIsEasy guide, but I get the fussee version error, but I have copied the 1.6.1 fusee.bin to the payloads folder. I also get a Old Nyx, there will be dragons error, but I can click through that one. What am I doing wrong?

you need to update your payload and your Hekate (bootloader folder)

 

[SciresM]

Happy June 15th!

 

[mrdude]

Happy June 15th!

Thanks for everything, and for keeping the switch alive.

 

[Lumince]

Was the crash from enabling prodinfo blanking looked into/fixed?

 

[impeeza]

Was the crash from enabling prodinfo blanking looked into/fixed?

Nop, you need to disable blank_prodinfo_* on e SDMC:/exosphere.ini file:

https://gbatemp.net/threads/nintendo-switch-firmware-version-17-0-0-released.641062/post-10277783

And I think also you need to restore your PRODINFO if you used Incognito_RCM

So remember to block your DNSs, Using Atmosphère DNSMitM and/or DNS90

 

[Lumince]

Nop, you need to disable blank_prodinfo_* on e SDMC:/exosphere.ini file:

https://gbatemp.net/threads/nintendo-switch-firmware-version-17-0-0-released.641062/post-10277783

And I think also you need to restore your PRODINFO if you used Incognito_RCM

So remember to block your DNSs, Using Atmosphère DNSMitM and/or DNS90

Well I am def not updating then wtf

 

[Deleted member 117573]

Nop, you need to disable blank_prodinfo_* on e SDMC:/exosphere.ini file:

https://gbatemp.net/threads/nintendo-switch-firmware-version-17-0-0-released.641062/post-10277783

And I think also you need to restore your PRODINFO if you used Incognito_RCM

So remember to block your DNSs, Using Atmosphère DNSMitM and/or DNS90

@impeeza,

I see you submitted a issue ticket on Incognito RCM being maintained by mistervampi requesting 17.0.0 support. Thanks for that. I used this in the past to blank my prodinfo on emunand but would like to restore it. Hopefully it will be updated, otherwise I guess I could always make a new emunand from my sysnand in which the prodinfo is intact.

 

[blindseer]

Was the crash from enabling prodinfo blanking looked into/fixed?

When exactly does the switch crash, I still have prodinfo blanking enabled from exosphere on 17 and havent had a crash yet?

 

[Deleted member 117573]

When exactly does the switch crash, I still have prodinfo blanking enabled from exosphere on 17 and havent had a crash yet?

Same. I have it blanked with Incognito RCM and use exosphere.ini to blank prodinfo. Granted I have only launched a few games/homebrew, but the games/homebrew start so I am not sure if it prevents launching or crashing during gameplay.

 

[blindseer]

Same. I have it blanked with Incognito RCM and use exosphere.ini to blank prodinfo. Granted I have only launched a few games/homebrew, but the games/homebrew start so I am not sure if it prevents launching or crashing during gameplay.

To be honest, other then dumping my game updates and firmware/keys I don't even use my switch anymore so its not a big deal, but Ive seen about the crashes but haven't had it happen on my end so was just wondering...

Edit: my launch switch is literally disintegrating so its just used so I can emulate at this point.

 

[impeeza]

@impeeza,

I see you submitted a issue ticket on Incognito RCM being maintained by mistervampi requesting 17.0.0 support. Thanks for that. I used this in the past to blank my prodinfo on emunand but would like to restore it. Hopefully it will be updated, otherwise I guess I could always make a new emunand from my sysnand in which the prodinfo is intact.

I haven updated my EmuNAND to FW 17, I am so far on 16.1.0 and the latest IncognitoRCM worked to backup, restore and blank the PRODUINFO, I don't know if works on FW 17, I don't think so.

When exactly does the switch crash, I still have prodinfo blanking enabled from exosphere on 17 and havent had a crash yet?

As far I know when you go online

 

[Deleted member 117573]

I haven updated my EmuNAND to FW 17, I am so far on 16.1.0 and the latest IncognitoRCM worked to backup, restore and blank the PRODUINFO, I don't know if works on FW 17, I don't think so.



As far I know when you go online

@impeeza,

I can verify it does not function under 17.0.0. I got a pkg1 error. Unless I am doing something else wrong.

 

[impeeza]

@impeeza,

I can verify it does not function under 17.0.0. I got a pkg1 error. Unless I am doing something else wrong.

yeah, the code have not the ID for 17, I am not a programmer, but can you please test this version:

 

[Deleted member 117573]

Sure.

Edit: Same pkg1 error.

 

[lolcatzuru]

i can boot into 17.0 just fine but i cant run any games, even though 1.6.2 indicates i should be able to? i can use homebrew just fine and even updated sigpatches and i have nothing.

 

[BaamAlex]

Was the crash from enabling prodinfo blanking looked into/fixed?

This is something he can't fix.

 

[Lumince]

This is something he can't fix.

I haven't seen him say that.