(USB HDD Update!) TX Anounces SX AUTOLOADER v1.10 from Team [WAIN]

0x3000027E · Nov 3, 2019

Reecey said:
Since when? I strongly disagree with you I have used exfat on 2 Nintendo Switch’s for a very longtime now I have never come across any issues with cfw booting, homebrew apps, xci emulation you name it not once! Your problem is not down to exfat, it’s down to cheap made MicroSD cards or “claimed” genuine MicroSD cards that are made in bad locations and bought generally online, nothing more! I would never buy a MicroSD card online I always purchase mine from the UK pcworld even if I have to pay premium prices but the point is I have never had an issue with any cards or “exfat” or any switch related issues.

Edit: also the sd reader in the Nintendo Switch is not very robust there not designed to have a MicroSD card shoved in & out the slot every 5 minutes. I had to change one on my first Switch but worked flawless with the new reader fitted.

I thought I was the only one who believed this...I had even given up the debate.

EmulateLife · Nov 3, 2019

I hate to even get into it again, but it's not only cheap sd cards that cause exfat corruption. I bought a legit card at a retail store that has worked 100% perfectly since I switched to Fat32 which was almost a year ago, but when I first got it it corrupted my entire sd card using exfat so I switched and never looked back. Just because nothing bad has happened to you personally, doesn't mean the issue is made up. Retroarch devs recommend Fat32, and they know what they're talking about.

I don't even understand why a SX OS user especially would even want to use exfat. They can just format an external hard drive to exfat (no corruption on externals) and install games to sd card or play them off external itself, and keep the sd card Fat32. The 4 gb limit was a problem in 2018 and has long been solved by now.

jkjj · Nov 3, 2019

its not an fat32/exfat issue

CaptainCPS-X · Nov 3, 2019

Finally was able to reproduce the "Error Code: 2168-0002" that users are reporting, but not on switch boot, just trying to "autoload" a XCI.

~~EDIT: I was NOT able to reproduce these errors on DOCKED MODE, only while detached.~~
EDIT2: I was able to reproduce DOCKED, after going to SXOS content manager twice, then when trying to "autoload" the message would popup.

Steps to reproduce it:

- If any USB storage is connected to the console, disconnect it first.
- Turn on the switch and reach the main menu (press button x3 if in lock screen)
- Connect USB storage device (mine has 300 XCIs at the moment, but should be enough to have like 50 for this test)
- Open SXOS content manager (Album)
- While the "Scanning..." message is displayed (press HOME button, do NOT press B)
- Try to mount "autoload" a game on the USB
- Error will be displayed and prompted to reboot the console

My theory why this is happening, I think that somewhere in the code the USB storage device is left with a open handle while scanning, and when HOME is pressed it is not intercepting this message and as a result, when another module try to access this open handle it crashes (?). Just a theory since I don't know the code behind this.

I haven't been able to reproduce the error on console boot tho', only this way.

Another error I was able to reproduce was as follows:

- If any USB storage is connected to the console, disconnect it first.
- Turn on the switch and reach the main menu (press button x3 if in lock screen)
- Go to configuration and disable lock screen on sleep
- Return to HOME screen
- Connect USB storage device (mine has 300 XCIs at the moment, but should be enough to have like 50 for this test)
- Press POWER button (just tap) to put the console to sleep
- Press POWER button again (just tap) to return from sleep, the console will reboot, instead of going to the login screen (I believe the error is the same as above, only that is happens when the console goes to sleep, so it can't be seen and it is waiting for the user to press POWER button to reboot).

Question for those having the Error Code: 2168-0002 on console boot

- Do you have the screen lock disabled on sleep? (please verify configuration)
- Try enabling the screen lock on sleep if disabled, and try again.

SeeYa!

Deleted User · Nov 3, 2019

CaptainCPS-X said:
Hi everyone! I am doing testing of different scenarios (300+ XCI files, blank XCI files, corrupted XCI files (random data)), and so far I haven't been able to reproduce the boot error.

You can see my test results here: -> link <-

I am trying to reproduce so maybe I can help in some way.

When reporting errors, it would be very nice to have detailed info in the following format:

SXOS: v2.9.2 (emuNAND)
FW: v9.0.0
Internal SD: exFAT
USB Storage: exFAT
Problem: Error with USB storage only
Details: I have my XCI files at "--specific location Internal or External (usb)--"

Those using mass USB storage devices with external power, make sure that it is not configured to sleep when data is not accessed, some USB storage devices have to be configured on a PC to remove that setting (SeaGate for example) they have custom tools to do so:

Image source: https://www.seagate.com/la/es/suppo...ilities-adjust-drive-sleep-interval-214217en/

SeeYa!

Tried it on 2 systems and on one I had 2 no boots past the switch logo and booted on next attempt:

SXOS: v2.9.2 (emuNAND)
FW: v9.0.1
Internal SD: exFAT
Problem: Internal SD Card
Details: XCI on root

CaptainCPS-X · Nov 3, 2019

ModderFokker619 said:
Tried it on 2 systems and on one I had 2 no boots past the switch logo and booted on next attempt:

SXOS: v2.9.2 (emuNAND)
FW: v9.0.1
Internal SD: exFAT
Problem: Internal SD Card
Details: XCI on root

Try moving the XCI files to ( sdroot:/sxos/xci ) (just move them, don't copy them, it is faster)

-How many XCI do you have?
-Do you have other files in the internal storage too, or just XCIs ? (such as NSP, etc)
-Is the console in docked or detached mode?

EDIT: I moved my internal XCI files to root as well, and did not get error, will try something else.

SeeYa!

comput3rus3r · Nov 3, 2019

Does anyone know if this works on sxos 2.8 with emunand on 8.1.0?

0x3000027E · Nov 3, 2019

EmulateLife said:
I hate to even get into it again, but it's not only cheap sd cards that cause exfat corruption. I bought a legit card at a retail store that has worked 100% perfectly since I switched to Fat32 which was almost a year ago, but when I first got it it corrupted my entire sd card using exfat so I switched and never looked back. Just because nothing bad has happened to you personally, doesn't mean the issue is made up. Retroarch devs recommend Fat32, and they know what they're talking about.

I don't even understand why a SX OS user especially would even want to use exfat. They can just format an external hard drive to exfat (no corruption on externals) and install games to sd card or play them off external itself, and keep the sd card Fat32. The 4 gb limit was a problem in 2018 and has long been solved by now.

No reason to debate it; everything has already been said.

EmulateLife · Nov 3, 2019

0x3000027E said:
No reason to debate it; everything has already been said.

Then your post wasn't even necessary. You're right though there's no reason to debate it using exfat on sd card on Switch is the wrong format. If it works for you good for you, but it's the only format that can cause corruption.

CaptainCPS-X · Nov 3, 2019

Just a recommendation, so we can be productive to the community and keep this clean, maybe opening another thread to talk about exFAT and FAT32, and everyone that wants to talk about that can go there.

The problem that some people are experiencing with Autoloader is not the format of the filesystem, is something else, and that is what I am trying to figure out, I don't have to, but I like to help ^___^.

SeeYa!

Deleted User · Nov 3, 2019

CaptainCPS-X said:
Try moving the XCI files to ( sdroot:/sxos/xci ) (just move them, don't copy them, it is faster)

-How many XCI do you have?
-Do you have other files in the internal storage too, or just XCIs ? (such as NSP, etc)
-Is the console in docked or detached mode?

EDIT: I moved my internal XCI files to root as well, and did not get error, will try something else.

SeeYa!

Was roughly 24 xci

No other nsps on sd card

Was in detached mode

Boots fine now but only this Switch failed to boot 2 times so far

CaptainCPS-X · Nov 3, 2019

ModderFokker619 said:
Was roughly 24 xci

No other nsps on sd card

Was in detached mode

Boots fine now but only this Switch failed to boot 2 times so far

Oh! nice to know! Thank you! will keep doing some testings and see if I can finally find what is the issue

EDIT: I tested adding unicode characters to a XCI file, but no error on boot, the file is not even processed. So it is not the naming of the files.

As a off-topic note, that is a feature many homebrews are missing, the handling of files with unicode names. At least I have reported this issue some weeks ago on the SXOS forums, so maybe they can add support for unicode in the future, haven't received reply from them.

SeeYa!

fluggy2013 · Nov 3, 2019

CaptainCPS-X · Nov 3, 2019

Guys filesystem doesn't have to do anything with Autoloader, Retroarch, etc. I have been using Retroarch on internal exFAT SD, without problems, I even use external exFAT SD using a USB card reader. Never had any problem.

So if anyone encounter problems, is because of them doing something wrong with the files / software / hardware.

You cannot blame a Operative System for corrupting a filesystem, if the user removed it without care (unmounting it, making sure nothing is happening in the background, reading or writing etc).

Again, I really recommend making a separate thread for this, since it is becoming like religion talk, just saying things by faith or beliefs, not really backing statements with technical support.

SeeYa!

KongsNutz · Nov 4, 2019

snoofly said:
exfat for the usbhdd storing your xcis is fine and in fact preferable to save having to split files
fat32 for the sd tho

^THIS

Reecey said:
Since when? I strongly disagree with you I have used exfat on 2 Nintendo Switch’s for a very longtime now I have never come across any issues with cfw booting, homebrew apps, xci emulation you name it not once! Your problem is not down to exfat, it’s down to cheap made MicroSD cards or “claimed” genuine MicroSD cards that are made in bad locations and bought generally online, nothing more! I would never buy a MicroSD card online I always purchase mine from the UK pcworld even if I have to pay premium prices but the point is I have never had an issue with any cards or “exfat” or any switch related issues.

Edit: also the sd reader in the Nintendo Switch is not very robust there not designed to have a MicroSD card shoved in & out the slot every 5 minutes. I had to change one on my first Switch but worked flawless with the new reader fitted.

You're wrong and it's been proven in the scene for a long time, do not use exfat if you use homebrew especially Retroarch. Or do, I'm just helping you out, it'll happen one day.

CaptainCPS-X · Nov 4, 2019

Autoloader v1.10 - Error Code: 2168-0002 (possible fix)

Found the problem that causes "Error Code: 2168-0002" on console boot, not letting you do anything.

- If your stuck on the error loop, just remove the SD card while the message is displayed
- Put the SD card on your pc (or some device that let you modify it)
- Make sure to have all these files / directories structure on your SD (simply by not having the cach and its subdirectories will make the error appear)

sd:/sxos/titles/00FF0012656180FF/cach
sd:/sxos/titles/00FF0012656180FF/cach/hdd
sd:/sxos/titles/00FF0012656180FF/cach/sd
sd:/sxos/titles/00FF0012656180FF/flags
sd:/sxos/titles/00FF0012656180FF/flags/boot2.flag
sd:/sxos/titles/00FF0012656180FF/exefs.nsp

- Insert the SD card back into the console
- Press the POWER button as the error indicates, to reboot the console
- Problem should be gone

Apparently the Autoloader doesn't have a module to check if the cach directory is present (or subdirectories), and wont create them either. So it would be a easy fix for the devs.

SeeYa!

Toph · Nov 4, 2019

Just leaving this here in case it could help someone else. I couldn't boot with the autoloader in place and would get an error screen on 2 different sd cards. Kept seeing the usual "your card is corrupted you need to format" nonsense. I thought that would be strange on 2 cards and one i had just formatted 3 days ago. Turned out on both I had to delete the "switch\checkpoint\saves" folder. Something in my saves in that folder caused it not to boot. After I did that it boots now on both sd cards and everything works as it should auto-loading xcis from usbhdd etc... all working good.

CaptainCPS-X · Nov 4, 2019

Toph said:
Just leaving this here in case it could help someone else. I couldn't boot with the autoloader in place and would get an error screen on 2 different sd cards. Kept seeing the usual "your card is corrupted you need to format" nonsense. I thought that would be strange on 2 cards and one i had just formatted 3 days ago. Turned out on both I had to delete the "switch\checkpoint\saves" folder. Something in my saves in that folder caused it not to boot. After I did that it boots now on both sd cards and everything works as it should auto-loading xcis from usbhdd etc... all working good.

Nice! good find and contribution! ^___^

SeeYa!

Tumbleweed · Nov 4, 2019

EmulateLife said:
I hate to even get into it again, but it's not only cheap sd cards that cause exfat corruption. I bought a legit card at a retail store that has worked 100% perfectly since I switched to Fat32 which was almost a year ago, but when I first got it it corrupted my entire sd card using exfat so I switched and never looked back. Just because nothing bad has happened to you personally, doesn't mean the issue is made up. Retroarch devs recommend Fat32, and they know what they're talking about.

I don't even understand why a SX OS user especially would even want to use exfat. They can just format an external hard drive to exfat (no corruption on externals) and install games to sd card or play them off external itself, and keep the sd card Fat32. The 4 gb limit was a problem in 2018 and has long been solved by now.

lmaol... who the fuck are u to tell SX users or any other CFW what is the right format to use? I’ve been using exfat on my SD Card since I bought my switch when it released and got it corrupted ONCE...the issue here has nothing to do with that this auto loader is clearly in “beta” if you don’t use homebrew you will never have corruptions, I used psnes and pfba and as mentioned had ONE single corruption. “Retroarch devs blablabla” this is a totally different thing as Retroarch works completely different and read/write a lot of data on your card. Don’t be arrogant saying you know what is the cause of the problem here because X/Y said it to you to not use exfat. I’m just being haughty to respond you in the same level you did.

EmulateLife · Nov 4, 2019

Tumbleweed said:
lmaol... who the fuck are u to tell SX users or any other CFW what is the right format to use? I’ve been using exfat on my SD Card since I bought my switch when it released and got it corrupted ONCE...the issue here has nothing to do with that this auto loader is clearly in “beta” if you don’t use homebrew you will never have corruptions, I used psnes and pfba and as mentioned had ONE single corruption. “Retroarch devs blablabla” this is a totally different thing as Retroarch works completely different and read/write a lot of data on your card. Don’t be arrogant saying you know what is the cause of the problem here because X/Y said it to you to not use exfat. I’m just being haughty to respond you in the same level you did.

Aww you butthurt that I stated a fact, because it is a fact.

exfat = corruption
Fat32 = no corruption

I said if it works for you great, butthurt clown.

You got corruption once because you were on exfat dumbass LMFAO because you cannot find one case of someone on Fat32 getting corruption. Any homebrew can cause corruption on exfat, that includes those standalone emulators. So get smarter you had corruption yet you're confronting me when I'm right and you're absolutely wrong.

Your iq must be really low.

Well-Known Member

Well-Known Member

Well-Known Member

Member

Deleted User

Guest

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Deleted User

Guest

Member

Well-Known Member

Member

[Team Oceanic]

Member

New Member

Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum