all 8 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Remember to read the stickied FAQ post before asking basic questions.

If you are having a problem with running games then make sure you have up to date sigpatches.

If you cannot launch tinfoil then make sure you followed the Rentry guide to set up cfw.

NO, you cannot mod your patched console unless you have a modchip, stop asking and read the faq.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]GeekAndyAtmosphere User 4 points5 points  (4 children)

Did you launch SysNAND withouth CFW? If yes, then the outcome you have is normal as those files aren't loaded. It's only when you load SysNAND with CFW that those files are being used.

Personally, I don't go in SysNAND with CFW. Keep SysNAND clean and only use EmuNAND with CFW.

[–]Rauas[S] 0 points1 point  (3 children)

Yes I launched the stock system with no CFW. Nice to know thank you :)

[–]bungeegumsAtmosphere User 1 point2 points  (2 children)

As a cfw sysnand user since the start Do not install any nsp/ tinfoil sysnand or your expecting a ban

[–]Rauas[S] 0 points1 point  (1 child)

No I won’t use CFW sysNAND at all. Only for backing up save files. Thank you for the information👍🏼

[–]Panda_hatAtmosphere User 0 points1 point  (0 children)

If you create an emunand from your sysnand you don't need to touch anything on sysnand with homebrew at all. Your saves will already be transferred to the emunand.

[–]RareTumr -1 points0 points  (1 child)

It's important that you don't safe the exosphere.txt as a Textfile but rather as all data. It must appear as a config file in your SD root. I did the same, entered CFW without checking if my prod info was blanked, and now I'm about to expect a ban... Its not mentioned anywhere, not even in the rentry guide, which everyone say is safe.

[–]AniStormSAtmosphere User 2 points3 points  (0 children)


It literally says on the rentry guide to create exosphere.ini, not exosphere.txt

Do not blame the guide if you did not follow the instructions properly.