Hacking WARNING MacOS Users !

[Lawletto]

I received my SXPRO Friday then I have done everything according to guides:

NAND Backup: no problem ; ChoidujourNX for Exfat support: no problem ; Emunand: no problem BUT

When I plugged back my SD Card into my Macbook pro in order to transfert Homebrews on it, a problem happened. So, I put my sd card back into my Switch and launch CFW with Emunand enabled and Blue Screen ! I took a moment to realise what could have gone wrong, then I managed to boot OFW with emunand disabled.

I decided to enable FTP Server in order to check on my Windows PC what was going on and I found that MacOS places hidden unvisible files with prefixes like "_." and those files are copies of the other files so you would have "payload.bin" and "_.payload.bin".

Those files are not visible on MacOS so you HAVE to connect your MicroSD card to a Windows pc in order to be able to see them and delete them because it will cause Blue Screens and prevent homebrews from working.

I hope this will help. I now use Filezilla and everything is ok now thanksfully.

 

[DeuX]

What will prevent homebrew from running is the archive bit. Hekate has an option to fix it for macOS users

 

[stewacide]

There's a "show hidden files" Finder plist flag you can enable if you want to see/delete them, also loads of utilities that accomplish the same.

 

[linuxares]

That's normal. That's how OSX journal the files. It makes those hidden _. folders. They show up like a source thumb in Windows or Linux.

EDIT: http://www.bresink.com/osx/TinkerTool.html with this tool you can disable OSX to write on for example USB devices with those folders. It's for spotight....

 

[Lawletto]

Thanks for the tips it'll help MacOS users but it is difficult to know that these things can happen because 99% of guides do no mention that.

This phenomenon should be highlighted because it is not a very common error and when it happens to you, and your files seem OK, it is difficult to find where is the issue.

 

[DeuX]

Its pretty common if you’re used to macOS

 

[Lawletto]

Its pretty common if you’re used to macOS

In a normal usage it's not a problem to have extra files like that, and most people don't know about it because it's not visible by default but it make you waste a lot of time or even money if you don't know what to do.

In my opinion, there should be much more warnings about it.

 

[Kafluke]

Thanks for the tips it'll help MacOS users but it is difficult to know that these things can happen because 99% of guides do no mention that.

This phenomenon should be highlighted because it is not a very common error and when it happens to you, and your files seem OK, it is difficult to find where is the issue.

Yes but this has been known for a while here. Ever since the first switch hack. If you would have just asked us we would have told you first.

 

[Lawletto]

Yes but this has been known for a while here. Ever since the first switch hack. If you would have just asked us we would have told you first.

The fact is that most guides including the ones on this website, do not warn people about the use of MacOs when creating emunand or installing homebrews.

There must be a lot of things that you know BECAUSE you were here since the first switch hack, but most people will expect guides to provide informations like that.

So, I just hope this will help people having troubles because of MacOS, I don't want to argue about the fact that everybody knows that or not.

 

[linuxares]

Most users don't have the issue since payloads ignore the _ folders

 

[spotanjo3]

I received my SXPRO Friday then I have done everything according to guides:

NAND Backup: no problem ; ChoidujourNX for Exfat support: no problem ; Emunand: no problem BUT

When I plugged back my SD Card into my Macbook pro in order to transfert Homebrews on it, a problem happened. So, I put my sd card back into my Switch and launch CFW with Emunand enabled and Blue Screen ! I took a moment to realise what could have gone wrong, then I managed to boot OFW with emunand disabled.

I decided to enable FTP Server in order to check on my Windows PC what was going on and I found that MacOS places hidden unvisible files with prefixes like "_." and those files are copies of the other files so you would have "payload.bin" and "_.payload.bin".

Those files are not visible on MacOS so you HAVE to connect your MicroSD card to a Windows pc in order to be able to see them and delete them because it will cause Blue Screens and prevent homebrews from working.

I hope this will help. I now use Filezilla and everything is ok now thanksfully.

It was mentioned somewhat already.. How to fix SD-Reading problems for macOS was there in the search engine. And SDCard cleanup script for MacOS users as well too. Nothing's new. I am macOS user and don't have a problem if you know what you re doing. Not good for macOS users who are noobs. I am an advance user so I know what I am doing and I am doing just fine. Love macOS!

 

[Lawletto]

It was mentioned somewhat already.. How to fix SD-Reading problems for macOS was there in the search engine. And SDCard cleanup script for MacOS users as well too. Nothing's new. I am macOS user and don't have a problem if you know what you re doing. Not good for macOS users who are noobs. I am an advance user so I know what I am doing and I am doing just fine. Love macOS!

I also love macOS but I'm not using it anymore for this kind of stuff

 

[spotanjo3]

I also love macOS but I'm not using it anymore for this kind of stuff

I am using it a lot with Switch. No problem for me at all. Just use Hekate to fixed this flag and you are all good to go. SMH.

 

[pLaYeR^^]

Wrong, there is a command which allows you to clean the external device from these files. Look here: http://tech.saigonist.com/b/osx/clean-mac-files-externalusb-disk.html

 

[DocKlokMan]

I just leave the ._ files on my SD, they don't affect anything for me. All major homebrew's ignore them and even SX OS ignores them on the XCI and NSP and homebrew screens. Honestly, the ._ files only posed a small problem for me in ReiNX when loading kips a long time ago and that got fixed too. Now I have no reason to remove the ._ files, everything still works perfectly fine.

 

[Lawletto]

I just leave the ._ files on my SD, they don't affect anything for me. All major homebrew's ignore them and even SX OS ignores them on the XCI and NSP and homebrew screens. Honestly, the ._ files only posed a small problem for me in ReiNX when loading kips a long time ago and that got fixed too. Now I have no reason to remove the ._ files, everything still works perfectly fine.

It's a problem when you are using emunand especially.

 

[AbuLela]

Just run this after you copy files to sd card, and stop the weeping -.-

sudo chflags -R arch /Volumes/YOUR_SD_CARD

 

[DeuX]

In a normal usage it's not a problem to have extra files like that, and most people don't know about it because it's not visible by default but it make you waste a lot of time or even money if you don't know what to do.

In my opinion, there should be much more warnings about it.

I think you’re getting it wrong. ._ files are not the issue, it’s the archive bit that prevents homebrew from running properly when using macOS. Either run Hekate ser archive bit option after transferring files or use ftp to send them over

 

[uyjulian]

Use dot_clean command line tool

 

[Lawletto]

This topic or another explaining how to use MacOs for cfw should be highlighted.

It would save people much trouble and save some time. Don't tell me they just have to make a simple research because no guide on how to install cfw ever talk about MacOs.