@impeeza , i understanf perfectly!I mean. NO! Any new model requiere hardware mod
@impeeza , i understanf perfectly!I mean. NO! Any new model requiere hardware mod
for me it is L+DDWN+R+R JOY CON INThe ones you have defynied for Tesla Overlays, the defaults for TESLA are L+DUP+R and for UltraHand Overlay ZL + ZR + DUP
"required firmware version" only matters for actual eshop, and maybe console to console update transfers. nsp installers ignore it, at that point the only limiting factor is sdk version used for the title, or the master key used to encrypt it depending on if you use fusee or hekate to bootApologies if this has already been asked, but is 19.0.1 stable with latest Atmosphere/Hekate and sigpatches/sys-patch? I know the latest Atmosphere has basic support for 19.0.0, and I assume 19.0.1 isn't that big of a change, but I just want to be sure. I'm mainly asking because it seems things are starting to require 19.0.1, such as the 1.0.1 update for Yakuza Kiwami, but I've seen reports that some NSPs that get detected as needing 19.0.0/19.0.1 sometimes still work on 18.1.0 (which I am still using on my modded v1 Switch). Any insight would be appreciated. Thanks in advance.
Oh nice. I'm still kinda weary about updating to FW 19. I figured if I installed a game/update that required 19 while I'm still on 18.1, it wouldn't boot after installing."required firmware version" only matters for actual eshop, and maybe console to console update transfers. nsp installers ignore it, at that point the only limiting factor is sdk version used for the title, or the master key used to encrypt it depending on if you use fusee or hekate to boot
even eshop wouldnt need to follow it, but by enforcing a newer firmware version to install or run updates it forces people to continue updating instead of staying behind
like, there's no technical reason that makes the newer firmware version "required". it's just a check that asks for firmware version, and the check just doesnt get done with most nsp installers
if you have AutoRCM you can press VOL- while booting to open NYX (Hekate's GUI)for me it is L+DDWN+R+R JOY CON IN
and what do you press again to get back into Hekate while it is booting? I'm trying to use Auto RCM now.
[Atmosphere - SysNAND]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
[Atmosphere - EmuNAND]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
[Stock SysNAND]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
never use premade packages, READ AND LEARN what you put on your console.I downloaded the HATS PACK on my switch and i use the overlay i see the color Orange on the syspatches , so It should be okay
Installing SYS-Patch https://gbatemp.net/download/sys-patch-sysmodule.38874/ and restarting the consoleHey guys I think I might have screwed up my switch.
I used to be an atmosphere only user.
After a long time I've recently
However I can't start most of my games anymore. Some Third party games still work, but the vast majority of nintendo games doesnt.
- updated my switch to Atmosphere 1.7.1|s
- updated switch Firmware to 18.1.0
- downloaded latest exefs_patches and kip_patches
Any idead how I could fix this?
sounds like whoever made the dumps for the games you downloaded is a dummy and put the master key revision byte in the ticket one byte too far ahead. so the ticket gets treated as temporary because master key revision is 0x10-0x1F (?) and gets invalidated after a rebootMy game asks me to connect to the internet in order for it to start. This happens only after I restart the console after playing it initially. I will have to delete the ticket and re-install the game to play it every time. How can I fix this?
This worked! I had no idea dbi even existed lol. The Russian build didn't bother me much either. It really is a powerful tool. It helped me identify tickets that I no longer needed on my console.sounds like whoever made the dumps for the games you downloaded is a dummy and put the master key revision byte in the ticket one byte too far ahead. so the ticket gets treated as temporary because master key revision is 0x10-0x1F (?) and gets invalidated after a reboot
the easy fix for this is to install using dbi, which is supposed to automatically fix this ticket error when you install. the more difficult fix is to dump the ticket and manually hex edit it, then reinstall it. you can dump the ticket through dbi and reinstall it also with dbi. the even more difficult fix is to get whoever is dumping games to understand that they're stupid so they can stop making that mistake
The serial number is only to tell if a console is a V1 unpatched or a v2 patched.@impeeza ,you mean serial number?
@impeeza thanks i understand,now i will tell everyone who asks me.The serial number is only to tell if a console is a V1 unpatched or a v2 patched.
But ANY lite and OLED is irremediable patched so the only way to install a CFW is using a hardware modchip
Hello I have a stupid question. Very recently I bought a modded lite everything was running fine until I got an error there was an issue with dat0, sent it to a professionnal they redid everything checked the connections everything was running fine until yesterday that im getting 1 long blue and short yellows (4 sometimes 6) and im pretty sure the chip is the issue. I asked the person that did my repair they say that we have to redo everything so thats more money which I don't have. My question is since all the flux was redone last week cant I simply just go and buy a new chip and only swap that out?
Even a "long" (1-2 cms extra) cable can create problemsIt's rare for the chip itself to be the problem. They are all almost the same. 95% of the time it's the soldering.
But to answer your question, yes it's likely that all the flex cables can just be inserted into a new chip. Assuming you get another lite modchip of the same variety as your current one. There are different kinds.
Again, I doubt this will fix it.
@masagrator I always wanted to know the same, what do you thinkHey, I've got a question about this Tesla overlay: https://github.com/EzWiz21/InfoNX
You can find a working version here, thanks to impeeza: https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/page-72#post-10121629
My question is: how do I enable the charging limit to 80%? And, is it normal that the battery anti-aging functionality keeps getting disabled? Every time I enter or exit a game, the overlay tells me it's off.