Hacking SWITCH NOOB PARADISE - Ask questions here

Thundereus · Jan 9, 2026

yin0203 said:
Error:2002-4686 010000000000001F
After shutdown the switch with Ultrahand plugin, and turn it on today when I boot to the CFW.

I checked the content folder, there is no one name 010000000000001F, and I tried to delete all file in the [content] folder, and the overlay items, still not able to boot to the CFW.

Any guys have this issue? How can I solve it?

I'm no professional and don't know what the error code means but when your system worked before I would suggest to rule out a hardware problem.
My ideas/suggestions in order of effort to fix the problem.

1. Go into Hekate - Tools - Archive RCM Touch Pkg1/2 and tap to "Fix Archive Bit".

2. You could also try letting windows checkdisk do a scan for errors on the sdcard but I doubt the filesystem to be the problem.

---------

3. Basically try to boot into a fresh installation of your homebrew setup.:

Make a backup of all folders, except "Nintendo" (As it is very big and you DON'T need to delete it for my suggestion.) Then delete everything else (Atmosphere related, NOT the "Nintendo" folder) and copy a fresh Atmosphere and software you need (Ultrahand, SaltyNX etc.).

Basically try to boot into a fresh installation of your homebrew setup. If it works copy your "config" folder from your backup onto the SD card and test if it boots then. If it doesn't the problem must be inside the config files, otherwise continue by copying the backed up "switch" folder onto the sd card and check if it works then. Slowly copy one part of the folder structure from your backup back to the sdcard and see when it crashes again.

When you find the problem, just copy everything else, except that folder or file that causes the crash and just reconfigure the lost settings manually.

Again: Don't delete your "Nintendo" folder. Only what comes with atmosphere. And backup everything before.

-----------

4. If all of this doesn't help and it still crashes try to boot into original HOS without atmosphere.

If it still crashes it might be a Dat0 problem. (At least this was the problem with my switch when it suddenly crashed after working well for weeks.)

Post automatically merged: Jan 9, 2026

jellydoger said:
Hi guys , sorry to ask but i have an issue that i tried to solve to no avail ( switch oled )

I currently have battery desync,
At first my battery has issue which is if i charge not full example (87-99%) the ui it suddenly will change to 100% automatically but it still run and turned off normally at 0%

Then i thought this must be the mismatched and after searching find the battery desync nx

I try to follow the guide there :
Open emummc - charge it to 100% - Open app - reset call - use it till low battery show up

In first step it cause new problem suddenly it shut down at 52% - i keep positive and think its part of process i charge it in hekate with the screen turn off. Btw when its on its already on 52% again. I charge it with saturation (6 hours )

On second cycle it turn off again in 51%

I think there is something wrong here.. is there any step that i misread

Thank you

Hi,
From my experience this can be really messy and annoying so it might take some attempts... But some nuances might help, because the fuel gauge is a bitch and needs time to calibrate when the battery is empty and full.

1. Reset fuel gauge with app. Leave app with "B" and close homebrew.

2. Connect charger and charge the console.

3. Important: When the battery is seemingly full (Ui showing 100%) open Ultrahand - StatusMonitor - Other - battery/charger and check what Raw Charge says. Let the console charge until Raw charge is 100% or the Current Flow drops to +-0mA. (Sometimes it shows some mA flowing but as long as it is just in the single digits it is just margin of error.)

4. When Raw charge and UI say 100% and there is no current being pushed in, let the console sit for 30 more minutes in sleep mode. Give the fuel gauge time to calibrate and save the values.

5. Disconnect the charger and let the console discharge in home menu. Don't use the console, don't use anything that raises the power draw and just turn the screen brightness to minimum.

6. Let the console dischararge and turn off by itself.

7. Wait for around 1 hour after it turned off (Let the fuel gauge save the "empty" status of the battery.) before doing anything.

8. Then connect the charger and boot again. Check if the percentage is around 1% - 5%.

If it is still very high (over 50%), check what the Raw Charge from Status Monitor says. If raw charge also says over 50% then something could be wrong with your hardware. What does the voltage say? Empty should be around 3,400V to 3,500V.

I don't know for sure if it will work but if it still turns off at around 50%, force it to turn on all the time until you get 0%. Drain that bastard with force until the hardware completely shuts down.
When it does so let it sit for an hour. Then charge it fully and don't boot into the system until it is full. (Except it boots automatically, then just let it is do it's job without touching. Just put it into sleep mode if you disabled auto sleep.) Then follow steps 3-8 again and see if it finally drops to 0% when discharging fully. (Or around 5% when it automatically shuts off.)

Additional info when checking the Raw charge:
The battery is full when the voltage is around 4,200V or at least between 4,165V and 4,250V, depending on your individual battery cells.
As mentioned above: The battery is fully charged when the voltage stays stable for a certain amount of time and when current isn't flowing constantly anymore (+XXmA).

That_Guy_Who · Jan 10, 2026

veggav said:
hey, I'm in a similar situation.

updated hekate.
updated atmosphere.
updated sigpatches.
update firmware to 21.1.0 using daybreak on emuNAND and some homebrew were not working.
downgradeded firmware to 20.5.0 using daybreak on emuNAND and now whenever I try to boot my emuCFW I get this same error.

Any chance someone could help 2 folks at the same since we have the exact same problem?

--------------------------------------------------------------------------------------

EDIT: found a fix

https://github.com/sthetix/DowngradeFixer

put the downgradefixer bin in bootloader/payloads
in hekate boot into downgradeFixer, fix emuMMC, reboot into hekate, boot into emuCFW.

Thanks man, I did the tasks manually after finding a Reddit post step by step. This looks way simpler

Defoxl · Jan 10, 2026

ERROR 0x290 (2144-0001)
Program ID: 0100000000001000
Process Name: qlaunch
Firmware: 14.1.0 (Atmosphère 1.3.1-master-62eb4d698)
this happen whenever i open the profile menu. i dont have theme install. already delete that folder the problem still exist

yin0203 · Jan 10, 2026

Thundereus said:
I'm no professional and don't know what the error code means but when your system worked before I would suggest to rule out a hardware problem.
My ideas/suggestions in order of effort to fix the problem.

1. Go into Hekate - Tools - Archive RCM Touch Pkg1/2 and tap to "Fix Archive Bit".

2. You could also try letting windows checkdisk do a scan for errors on the sdcard but I doubt the filesystem to be the problem.

---------

3. Basically try to boot into a fresh installation of your homebrew setup.:

Make a backup of all folders, except "Nintendo" (As it is very big and you DON'T need to delete it for my suggestion.) Then delete everything else (Atmosphere related, NOT the "Nintendo" folder) and copy a fresh Atmosphere and software you need (Ultrahand, SaltyNX etc.).

Basically try to boot into a fresh installation of your homebrew setup. If it works copy your "config" folder from your backup onto the SD card and test if it boots then. If it doesn't the problem must be inside the config files, otherwise continue by copying the backed up "switch" folder onto the sd card and check if it works then. Slowly copy one part of the folder structure from your backup back to the sdcard and see when it crashes again.

When you find the problem, just copy everything else, except that folder or file that causes the crash and just reconfigure the lost settings manually.

Again: Don't delete your "Nintendo" folder. Only what comes with atmosphere. And backup everything before.

-----------

4. If all of this doesn't help and it still crashes try to boot into original HOS without atmosphere.

If it still crashes it might be a Dat0 problem. (At least this was the problem with my switch when it suddenly crashed after working well for weeks.)

Post automatically merged: Jan 9, 2026

Hi,
From my experience this can be really messy and annoying so it might take some attempts... But some nuances might help, because the fuel gauge is a bitch and needs time to calibrate when the battery is empty and full.

1. Reset fuel gauge with app. Leave app with "B" and close homebrew.

2. Connect charger and charge the console.

3. Important: When the battery is seemingly full (Ui showing 100%) open Ultrahand - StatusMonitor - Other - battery/charger and check what Raw Charge says. Let the console charge until Raw charge is 100% or the Current Flow drops to +-0mA. (Sometimes it shows some mA flowing but as long as it is just in the single digits it is just margin of error.)

4. When Raw charge and UI say 100% and there is no current being pushed in, let the console sit for 30 more minutes in sleep mode. Give the fuel gauge time to calibrate and save the values.

5. Disconnect the charger and let the console discharge in home menu. Don't use the console, don't use anything that raises the power draw and just turn the screen brightness to minimum.

6. Let the console dischararge and turn off by itself.

7. Wait for around 1 hour after it turned off (Let the fuel gauge save the "empty" status of the battery.) before doing anything.

8. Then connect the charger and boot again. Check if the percentage is around 1% - 5%.

If it is still very high (over 50%), check what the Raw Charge from Status Monitor says. If raw charge also says over 50% then something could be wrong with your hardware. What does the voltage say? Empty should be around 3,400V to 3,500V.

I don't know for sure if it will work but if it still turns off at around 50%, force it to turn on all the time until you get 0%. Drain that bastard with force until the hardware completely shuts down.
When it does so let it sit for an hour. Then charge it fully and don't boot into the system until it is full. (Except it boots automatically, then just let it is do it's job without touching. Just put it into sleep mode if you disabled auto sleep.) Then follow steps 3-8 again and see if it finally drops to 0% when discharging fully. (Or around 5% when it automatically shuts off.)

Additional info when checking the Raw charge:
The battery is full when the voltage is around 4,200V or at least between 4,165V and 4,250V, depending on your individual battery cells.
As mentioned above: The battery is fully charged when the voltage stays stable for a certain amount of time and when current isn't flowing constantly anymore (+XXmA).

Really appreciate your reply, will try it!
I did the fix archive bit trick, and still not able to boot in to the atmosphere.

Is there any way to copy the save under this situation? (mean cannot boot in to the emunand)

Post automatically merged: Jan 10, 2026

Thundereus said:
I'm no professional and don't know what the error code means but when your system worked before I would suggest to rule out a hardware problem.
My ideas/suggestions in order of effort to fix the problem.

1. Go into Hekate - Tools - Archive RCM Touch Pkg1/2 and tap to "Fix Archive Bit".

2. You could also try letting windows checkdisk do a scan for errors on the sdcard but I doubt the filesystem to be the problem.

---------

3. Basically try to boot into a fresh installation of your homebrew setup.:

Make a backup of all folders, except "Nintendo" (As it is very big and you DON'T need to delete it for my suggestion.) Then delete everything else (Atmosphere related, NOT the "Nintendo" folder) and copy a fresh Atmosphere and software you need (Ultrahand, SaltyNX etc.).

Basically try to boot into a fresh installation of your homebrew setup. If it works copy your "config" folder from your backup onto the SD card and test if it boots then. If it doesn't the problem must be inside the config files, otherwise continue by copying the backed up "switch" folder onto the sd card and check if it works then. Slowly copy one part of the folder structure from your backup back to the sdcard and see when it crashes again.

When you find the problem, just copy everything else, except that folder or file that causes the crash and just reconfigure the lost settings manually.

Again: Don't delete your "Nintendo" folder. Only what comes with atmosphere. And backup everything before.

-----------

4. If all of this doesn't help and it still crashes try to boot into original HOS without atmosphere.

If it still crashes it might be a Dat0 problem. (At least this was the problem with my switch when it suddenly crashed after working well for weeks.)

Post automatically merged: Jan 9, 2026

Hi,
From my experience this can be really messy and annoying so it might take some attempts... But some nuances might help, because the fuel gauge is a bitch and needs time to calibrate when the battery is empty and full.

1. Reset fuel gauge with app. Leave app with "B" and close homebrew.

2. Connect charger and charge the console.

3. Important: When the battery is seemingly full (Ui showing 100%) open Ultrahand - StatusMonitor - Other - battery/charger and check what Raw Charge says. Let the console charge until Raw charge is 100% or the Current Flow drops to +-0mA. (Sometimes it shows some mA flowing but as long as it is just in the single digits it is just margin of error.)

4. When Raw charge and UI say 100% and there is no current being pushed in, let the console sit for 30 more minutes in sleep mode. Give the fuel gauge time to calibrate and save the values.

5. Disconnect the charger and let the console discharge in home menu. Don't use the console, don't use anything that raises the power draw and just turn the screen brightness to minimum.

6. Let the console dischararge and turn off by itself.

7. Wait for around 1 hour after it turned off (Let the fuel gauge save the "empty" status of the battery.) before doing anything.

8. Then connect the charger and boot again. Check if the percentage is around 1% - 5%.

If it is still very high (over 50%), check what the Raw Charge from Status Monitor says. If raw charge also says over 50% then something could be wrong with your hardware. What does the voltage say? Empty should be around 3,400V to 3,500V.

I don't know for sure if it will work but if it still turns off at around 50%, force it to turn on all the time until you get 0%. Drain that bastard with force until the hardware completely shuts down.
When it does so let it sit for an hour. Then charge it fully and don't boot into the system until it is full. (Except it boots automatically, then just let it is do it's job without touching. Just put it into sleep mode if you disabled auto sleep.) Then follow steps 3-8 again and see if it finally drops to 0% when discharging fully. (Or around 5% when it automatically shuts off.)

Additional info when checking the Raw charge:
The battery is full when the voltage is around 4,200V or at least between 4,165V and 4,250V, depending on your individual battery cells.
As mentioned above: The battery is fully charged when the voltage stays stable for a certain amount of time and when current isn't flowing constantly anymore (+XXmA).

Tried your ways to do, and still showing the same error.
Sigh, seem no way to fix it.

mspy · Jan 12, 2026

Migrating from a sdcard to a bigger sdcard is as simple as copying all the contents of 1 card to another?
Like in windows drag and drop everything from 1 card to another and all will work fine?

None101 · Jan 12, 2026

Hey guys I’m having 2 small issues:

1 is my switch lite (picofoly) crashes when in rest mode sometimes if leaving it for long periods untouched.

2 CFW does not work and I get a boot loader error which I will post here (although semi stock and the other two do work fine)

Xellos2099 · Jan 12, 2026

Question. What is currently the best emulator for switch n steamdeck? I try using emudeck but run into prod key and firmware issue

Glomgold · Jan 13, 2026

So I hacked my first Switch (softmod). I'm wondering if I did something stupid. I was forced to do a system update to do this:

"If you choose the emuMMC path introduced later in the guide, it'll be important to disable the Automatic Save Data Cloud function beforehand, as well as making sure the Switch is set as the primary Pass-Enabled console."

I'm om 21.1.0, I just avoided 21.2.0. My user is now linked to a Nintendo account, this is also present on emuMMC.

Is this okey?

I tried to install a game with Awoo via USB but it failed.

What should I use to install games? Tinfoil, dbi, awoo?

I finally managed to install a game with awoo, I put the file on the SD card, is there a downside to doing this compared to installing over USB?

Thundereus · Jan 14, 2026

yin0203 said:
Really appreciate your reply, will try it!
I did the fix archive bit trick, and still not able to boot in to the atmosphere.

Is there any way to copy the save under this situation? (mean cannot boot in to the emunand)

Post automatically merged: Jan 10, 2026

Tried your ways to do, and still showing the same error.
Sigh, seem no way to fix it.

Heya, thanks for trying out my solutions.
If the system still crashes even if you installed a fresh atmosphere without any old configuration it could be a hardwawre problem. A few months ago I had the same. Suddenly the system crashed every time and showed me an atmopshere error screen. In the end my modder guy had to do the Kamikaze mod to make it work again. It was the Dat0 cable from the memory chip that was a piece of crap. I generally heard that the normal flex plate method can be unreliable.

But to be sure: Do you also get a crash when trying to boot into original Nintendo Firmware (HOS)? If yes, then I am almost pretty sure it is the DAT0 connection. But your modder should check out what the problem could be if it doesn't seem to be the Dat0. But it is unlikely to be the chip or the flex cables on the SoC. Maybe it could also be a dead capacitor, one of those tiny ones north of the memory section?

Post automatically merged: Jan 14, 2026

Glomgold said:
So I hacked my first Switch (softmod). I'm wondering if I did something stupid. I was forced to do a system update to do this:

"If you choose the emuMMC path introduced later in the guide, it'll be important to disable the Automatic Save Data Cloud function beforehand, as well as making sure the Switch is set as the primary Pass-Enabled console."

I'm om 21.1.0, I just avoided 21.2.0. My user is now linked to a Nintendo account, this is also present on emuMMC.

Is this okey?

I tried to install a game with Awoo via USB but it failed.

What should I use to install games? Tinfoil, dbi, awoo?

I finally managed to install a game with awoo, I put the file on the SD card, is there a downside to doing this compared to installing over USB?

If you followed the guide you should have placed the emummc.txt in /atmosphere/hosts which should block all connections to the nintendo Server. The connection of your account shouldn't be a problem but you can relink it to a virtual one with the app "linklho" if you have any problems (When games don't boot when choosing that profile or anything else that causes freezes or crashes when it tries to connect to it.)

EmuMMC is a completely seperate instance of your system exclusively on your sdcard. So nothing is synced with the internal memory. (Even if you chose to install something on the internal memory it will be just put onto the SD card, just in a different folder. It is fully simulating the environment of the switch and also behaving as if the sdcard is the internal memory.)

I would recommend to use DBI and MTP responder. Then just drag&drop your NSP or XCI files into "SD Card Install" or "NAND install", depending on where you have more space left as emunand still uses the same size like the console has internally.
At least this is what I use since Goldleaf was unreliable and I didn't want to mess with Tinfoil or another app if DBI does it perfectly well without extra PC software.

There should be no difference which method you use to install a game. What matters is if the file is not corrupted/damaged and if the system says that it was installed successfully. If you still have problem, download from a different source or install directly from a cartridge if available.

Post automatically merged: Jan 14, 2026

None101 said:
Hey guys I’m having 2 small issues:

1 is my switch lite (picofoly) crashes when in rest mode sometimes if leaving it for long periods untouched.

2 CFW does not work and I get a boot loader error which I will post here (although semi stock and the other two do work fine)

Let your modder check if the capacitors are not dead or if the Dat0 connection is working. I assume a modding/hardware problem.
Mine also died without any appearent reason. The flex plate under the memory chip can suddenly lose connection to the pin from heat cycles, at least I have heard that and experienced it myself without doing anything to provoke the failure.

Oso · Jan 14, 2026

Hello, I have just been banned from online services with a console that I have been using for years with cfw in sysnand. I had internet enabled for file transfers and lots of other stuff...

Today I wanted to play, so I did the update (I hadn't used the console in a very long time) and after that I got error message 2124-4508. The associated Nintendo account is not banned. All I know is that when the game Pokémon ZA came out, I downloaded the XCI and installed it on my Switch, played a little, and then deleted the game. Is Nintendo banning me because I saved a pirated game? I don't really care that the console is banned, but I'd like to know why this is happening to me only right now.

That_Guy_Who · Jan 16, 2026

Strange issue I’ve started to have
Hi, I’m trying to set up a new a new SD Card on my Modded Oled switch. (Long story as to why).
So, fresh memory card, wiped to fat32, HATS pack put in root, then on the switch - card partitioned and then EmMMC set up. When putting the memory card back in my PC it’s now not readable. Windows states it needs formatting. I’ve tried this on 2 different cards and it’s the same result.
I’m using Rufus to format my cards.
Any ideas where the issues lie?
Thanks

Update: resolved!

SamyKn · Jan 16, 2026

I'm building a new larger size sd card (Atmosphere 1.10.2 , Hekate 6.5), installed HATs Pack and run through process fine but i have few major issues:

- It detects the parental setting from the OFW and whatever i run it prompts for parental control , not sure how?!
- I create Shortcuts using NSP forwarder but fails to run , same working fine on the old SD card fine. (i created forwarders using the same prodkey from Hekate 6.4.2)
- Also It detects the games installed on the OFW side

, I'm running EMUMMC as I understand dangers of running SYSMMMC on EMUMMC.

Appreciate any help.
Thanks!

ZAA · Jan 16, 2026

Hello-
i have the latest atmosphere, hekate and fusebin
when trying to load via CFW sysand i am only getting a black screen
any advice is much appreciated

this is what i currrently have in hekate_ipl.ini:

[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100

{DeepSea}
{Github: https://github.com/orgs/Team-Neptune/}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

rubinorosso93 · Jan 16, 2026

hi guys, i'm on 20.4.0, AMS 19.5, and i'm using edizon 3.1.0. nightly. it works good (i'm use it to backup and resore saves), but after last update, the icons of games are all messed up. It can be fixed? or can u suggest me a different program that does the same? thanks

Glomgold · Jan 16, 2026

Getting "game update" prompt everytime, how can I remove it? I tried putting the console in airplane mode and boot into recovery mode and exit, didn't do anything.

forgotten-865 · Jan 16, 2026

How bad is fake RCM Loader ? Sometimes I lose access to my smartphone and laptop and because of that I can't use payload injector

realbout · Jan 18, 2026

Hello everyone,

I was just about to update my Switch. The goal is Atmosphère 1.10.2 and firmware 21.0.0.

Currently installed are: Atmosphère 1.9.1 and firmware 20.1.0.

Until now, I have always simply turned off the Switch, removed the SD card, and copied the relevant folders onto it. In this case:
Everything from the archives

- atmosphere-1.10.2-master-eb34f9789+hbl-2.4.5+hbmenu-3.6.1.zip
- Hekate+AMS-package3-sigpatches-1.10.2P-cfw-21.2.0_V0.zip
- hekate_ctcaer_6.5.0_Nyx_1.9.0.zip
- Firmware 21.0.0

But when I try to boot with the SD card, I get the following error:

Does anyone know what the problem is? Until now, I always copied all the new files first and then updated the Switch firmware with daybreak.

Thank you in advance for your help.

Blythe93 · Jan 18, 2026

realbout said:
Hello everyone,

I was just about to update my Switch. The goal is Atmosphère 1.10.2 and firmware 21.0.0.

Currently installed are: Atmosphère 1.9.1 and firmware 20.1.0.

Until now, I have always simply turned off the Switch, removed the SD card, and copied the relevant folders onto it. In this case:
Everything from the archives

- atmosphere-1.10.2-master-eb34f9789+hbl-2.4.5+hbmenu-3.6.1.zip
- Hekate+AMS-package3-sigpatches-1.10.2P-cfw-21.2.0_V0.zip
- hekate_ctcaer_6.5.0_Nyx_1.9.0.zip
- Firmware 21.0.0

But when I try to boot with the SD card, I get the following error:

View attachment 551735

Does anyone know what the problem is? Until now, I always copied all the new files first and then updated the Switch firmware with daybreak.

Thank you in advance for your help.

I'd advise against using unofficial Atmosphere builds if you don't know what you're doing.

I'm currently on AMS 1.10.1, hekate v6.4.2 and firmware 21.1.0 and everything seems to be running fine, except for a few homebrew apps that may need another fix or two. Latest hekate v6.5.0 might have some issues with the Erista consoles among other things so wait for a bit newer release with bugs hopefully fixed. Never update to the latest & greatest unless you're willing to deal with the bugs and everything.

As for the error you're getting, that might be related to the outdated module you're using, sys-clk perhaps? Never forget to update your sys-modules to the latest versions as they are usually the culprits behind many Atmosphere crashes.

EDIT: I'd also suggest that you use sys-patch instead of sigpatches. Ever since I switched to sys-patch I can't recall ever having an issue with any of the games I've tried to play. You can also have both, it will work, but I'd recommend sticking to the one of the two.

phillyrider807 · Jan 18, 2026

Hey everyone. Running into a problem here. I updated my switch to latest update so i can get back to playing online. But doing so has made my emunand come up as a black screen.

Stock and CFW sysnand still works.

Any help on getting my emunand working again? As of now my sysnand is on a higher version then my emunand. Is that the reason it's no longer booting?

Blythe93 · Jan 18, 2026

phillyrider807 said:
Hey everyone. Running into a problem here. I updated my switch to latest update so i can get back to playing online. But doing so has made my emunand come up as a black screen.

Stock and CFW sysnand still works.

Any help on getting my emunand working again? As of now my sysnand is on a higher version then my emunand. Is that the reason it's no longer booting?

I wonder if this will fix your issue: https://github.com/CTCaer/hekate/issues/1186#issuecomment-3755993083

Hacking SWITCH NOOB PARADISE - Ask questions here

Member

Error:2002-4686 010000000000001F​

Member

Member

New Member

Well-Known Member

New Member

Attachments

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Member

Active Member

The Treasure Tracker

Well-Known Member

The Treasure Tracker

Similar threads

Popular threads in this forum

Error:2002-4686 010000000000001F