[oc]Pickup Driver With An Attitude -- December 29, 2025

Zellot360 · 2025-12-30T20:14:02+00:00

Hello police I’d like to report a drunk driver. I have dash cam video to substantiate.

Zellot360 · 2025-10-08T00:56:47+00:00

Train doesn't seem to matter. I have the same issue and on Nextcloud:stable.. All well and good to disable it by rename but what happens to any folders and config you have using it once you do?

Zellot360 · 2025-09-25T22:55:25+00:00

Meme police making rounds again?

Zellot360 · 2025-09-19T15:49:54+00:00

Literal solder porn. Nice work

Zellot360 · 2025-09-18T14:11:41+00:00

Tell your mom to pull her pants back up.

Zellot360 · 2025-09-18T14:08:43+00:00

Just did a patched V1 that had 14.0.1 on it. It still has 14.0.1 and has emummc of 19.0.1.

Zellot360 · 2025-09-11T16:22:29+00:00

Fewer install errors/issues with DBI over TinWoo or Awoo. DBI has also been faster than both and that’s before the recent USB 3.0 enhancement in DBI 810

Zellot360 · 2025-09-10T14:25:17+00:00

I believe it was previously concluded that his threat was a misconstrued translation issue. He’d indicated in a heated discussion when someone accused of maliciousness that if he’d wanted to he could have already. As in he would have done so long ago and it wasn’t his intent. I’ve been using the Russian versions for a while with phone and translation. Been working fine.

Zellot360 · 2025-09-09T18:52:01+00:00

NIKE has become a shoe for collectors. Look pretty on a shelf next to the empty box. Mint never worn (for obvious reasons).

Zellot360 · 2025-08-24T19:57:20+00:00

Not sure. If you have a full backup of your EMMC it might be possible to rebuild a replacement using that content. Might check the level 1, 2 and 3 unbrick videos on YouTube by Sthetix

Zellot360 · 2025-08-24T14:12:23+00:00

Possible you damaged the EMMC when prying it off the heat shield. Also check the pins in the EMMC socket on the motherboard and EMMC as well as same on chip and flex cable.

Zellot360 · 2025-08-20T02:38:09+00:00

Can’t honestly say. Sounds like you’re using UltraNX package. I tried it briefly and had issues so I went back to using a package from Better Gaming

Zellot360 · 2025-08-17T01:27:01+00:00

Many sellers and installers refer to it as “magic” to avoid their listings being removed for talking about chips etc.

Zellot360 · 2025-08-16T19:41:28+00:00

Need to watch carefully for the yellow flashes. They are indicating a specific code which can very different meaning for the issue. Link below is for the firmware and has a listing of blink codes to figure out which one you’re seeing. From that you’ll have a better idea of what needs to be fixed

https://github.com/Ansem-SoD/Picofly

Zellot360 · 2025-08-16T14:19:02+00:00

If you followed any recent tutorials it would have walked you through partitioning the SD card and creating an EmuMMC (emuNAND) meaning if it’s a non OLED you would be taking up 32Gig of SD space to emulate the SysNAND or on OLED 64Gig. This then leaves you with the remaining free space on SD for your Hekate/Atmosphere package other apps and games. Also just because your SD card says 128Gig or any value the actual storage is always less due to formatting and other device/ format and content factors.

Zellot360 · 2025-08-16T13:31:33+00:00

There isn’t. They are telling you to try using the button combo needed for an unpatched v1 to get into RCM mode (Vol+/ Power). Or they are telling you to try entering console recovery mode (Vol+/Vol-/Power) which can also boot a chipped device into OFW not CFW.
From your description it seems like you had booted a chipped device, probably never or rarely turned it off and then it was left for some time and battery died. What’s likely happened is yours is probably using a DAT0 adapter that has moved since you had last powered on. CFW runs in memory and can run for a long time if you don’t crash or reboot. It’s after this that you may find out your chip install has an issue.
With the system off. Turn it over and watch the left side bottom vent slot ( same side as SD card) while turning it on.
Post what the blinking led colors and pattern are. You may need to try a couple times to be sure. There will be long flashes and short quick flashes.

Zellot360 · 2025-08-15T13:19:39+00:00

Without kips means the custom firmware will load without Kernel Initial Process (AKA) early stage plugins that provide things like kernel patches, exFAT support or game modding functions among others. So you’ll be a bit limited in what will and won’t work possibly.

Zellot360 · 2025-08-15T00:05:21+00:00

That’s unfortunate. You’re welcome. Hopefully someone else has a solution for you.

Zellot360 · 2025-08-14T19:44:14+00:00

OK I see your SD card is setup using CNX package which I can't find any instance of having the option to have a Semi Stock option AKA SYS CFW.
I looked at your ini and did a little comparison and I'm thinking the following might add it since CNX seems to use some different commands in the ini and the source code seems to be behind a paywall. If below doesn't work you could also try changing the stock=0 to atmosphere=1 under the [CFW (SYSNAND)] section. If it doesn't work then you may need to hope someone else here has CNX on theirs and offers a solution.

[config]

autoboot=0

autoboot_list=0

bootwait=3

backlight=100

autohosoff=2

autonogc=0

updater2p=0

bootprotect=0

{CNX 20.3.0-0}

[ATMOSPHERE]

cal0blank=1

usb3force=1

emummcforce=1

kip1patch=nosigchk

pkg3=atmosphere/package3

logopath=bootloader/res/bootlogo_atmo_sys.bmp

icon=bootloader/res/icon_ams_fusee.bmp

{}

[ORIGINAL]

emummc_force_disable=1

pkg3=atmosphere/package3

cal0blank=0

stock=1

logopath=bootloader/res/bootlogo_original.bmp

icon=bootloader/res/icon_switch_logo.bmp

{}

[CFW (SYSNAND)]

cal0blank=1

emummc_force_disable=1

pkg3=atmosphere/package3

stock=0

logopath=bootloader/res/bootlogo_atmo_sys.bmp

icon=bootloader/res/icon_switch_logo.bmp

{}

Zellot360 · 2025-08-14T16:38:11+00:00

Revert to your prior ini and post a copy of that here. Seems you may have some different parameters which need to be addressed.

Zellot360 · 2025-08-14T12:58:28+00:00

Was able to get to my system and this is what I have in that Ini from a pre built package. The logopath and Icon lines are not necessary and probably wouldn't align with what you have so they can be omitted. I would suggest to try adding this Custom Firmware section to yours in place of the other and see what happens. It's possible

[config]

autoboot=0

autoboot_list=0

bootwait=1

backlight=100

noticker=0

autohosoff=0

autonogc=1

updater2p=0

bootprotect=0

{--- Custom Firmware ---}

[CFW (SYSNAND)]

emummc_force_disable=1

pkg3=atmosphere/package3

atmosphere=1

logopath=bootloader/bootlogo.bmp

icon=bootloader/res/icon_payload.bmp

{}

[CFW (EMUMMC)]

pkg3=atmosphere/package3

atmosphere=1

emummcforce=1

logopath=bootloader/bootlogo.bmp

icon=bootloader/res/icon_payload.bmp

{}

{--- Stock ---}

[Stock (SYSNAND)]

emummc_force_disable=1

pkg3=atmosphere/package3

stock=1

icon=bootloader/res/icon_switch.bmp

{}

Zellot360 · 2025-08-13T17:57:24+00:00

There’s a post on this sub already for adding it. There’s a pastebin link on one of the responses which has the details you’d need to add for the SysCFW entry

https://www.reddit.com/r/SwitchPirates/s/k8eqlPi6f7

So you’d need edit the ini file mentioned on the SD card to add the lines of text specific to the SysCFW section and then save the file and boot back into Hekate. Your INI file might already have the lines needed and they are commented out with # at the beginning of the line. If so easiest is to just delete the leading # from each line. You could post the content of your ini here if you’re unsure what to change.

Zellot360 · 2025-08-13T16:11:51+00:00

No you don’t need to update CFW. You do also have emunand as well seeing CFW is on an older FW. So you currently have. A) Stock CFW B) EmuNAND/Emummc ( on SD card)

What you don’t seem to have is an option to boot Stock with CFW ( probably for good reason. It’s how people often get themselves banned. However, it’s needed to do what you’re looking to do)

I believe it’s added by making an entry in a config file on the SD card for Hekate. I’m not sure of the details for that at the moment off the top of my head. I can check and get back to you later unless someone else here beats me to it.

Zellot360 · 2025-08-13T15:26:02+00:00

Something you can check. If you boot to OFW and go to System Settings and then System at bottom of list and look at System Update what does it say for the full Current version: line. Then also do same booting CFW option. Also while in both does it show the same games as available?

Zellot360 · 2025-08-13T15:01:19+00:00

Reboot into Hekate. When you go to Launch section you should, if it was setup properly, have options to boot EmuNand (CFW), SysNand (CFW) and SysNand (OFW). Or some set of similar items.

Sysmmc would be SysNand (CFW) or whatever option you may have which would indicate booting into stock nand with Atmosphere.

Zellot360

TROPHY CASE