Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,123,602
  • Replies Replies 47,977
  • Likes Likes 66
Why?
Post automatically merged:
As mentioned in my post, I am an idiot for not doing any research first. I just selected the latest FW and updated. I was on 15. Thanks for the link.
What happens if in hekate you go to payloads and select fusee.bin you should have placed the latest fusee.bin in SD/bootloader/payloads from the atmosphere release download i know there is a fix for your issue i just cant remember what it is someone else should know. Actually does your hekate_ipl.ini have this line in it kip1patch=nosigchk
I was able to bypass the nosigchk error by selecting the fusee.bin payload. Yea!
Also my hekate*.ini file does have the line you wrote.

Now if I can just get my Tinfoil to work! But as I understand it, many people are having issues with Tinfoil on 19.0.0.
So I guess it's just a waiting game.

Thank you!
 
  • Like
Reactions: Blythe93
Hi, everyone.
I just want to ask if I can reboot to hekate (to upgrade my firmware) without turning off my switch? I had problems before trying to turning it back on again when I turn off my switch because I don't play it for a long time. So now I keep it on sleep mode just to be on the safe side.

I bought a premodded OLED Switch.
And I want to update my firmware to play newer games.

Thanks before
 
Hi, everyone.
I just want to ask if I can reboot to hekate (to upgrade my firmware) without turning off my switch? I had problems before trying to turning it back on again when I turn off my switch because I don't play it for a long time. So now I keep it on sleep mode just to be on the safe side.

I bought a premodded OLED Switch.
And I want to update my firmware to play newer games.

Thanks before
Yes you can reboot your console and press VOL- to launch NYX (Hekate's GUI).
Post automatically merged:

Yes you can reboot your console and press VOL- to launch NYX (Hekate's GUI).
I personally use the Tesla Overlay «Studios Pancake» which allows me to boot to NYX's UMS, or a hekate config or any payload. from the HOS.
 
  • Like
Reactions: Blythe93 and SkyeS
Yes you can reboot your console and press VOL- to launch NYX (Hekate's GUI).
Post automatically merged:


I personally use the Tesla Overlay «Studios Pancake» which allows me to boot to NYX's UMS, or a hekate config or any payload. from the HOS.
Ok thanks.. I'll look into it
 
I got a 2002-3539 and black screen issue. This is after updating my ofw firmware to 19 and atmosphere to 18.

I am able to go into EMUMMC and play games etc.
On Stock SYSNAND I get a black screen after the Nintendo logo.
I get the 2002-3539 error when I want to go into CFW Sysnand.
I've spent two days trying to fix this issue. Im losing my mind. I dont want to do a system wipe.
 
Hi folks. After updating to 19.0, installing Atmosphere 1.8.0 on my SD card, I get the error "Failed to open payload bin" when opening my Switch Oled.

I would be happy if you help me solve the problem.

My files on SD card,

ehehehe.png
 
Last edited by Directtor,
on the hekate github repository, the same place you should downloaded the hekate for update it!
Now I downloaded hekate v6.2.2 and replaced bootloader file. I changed the name of hekate ctcaer 6.2.2 to payload.bin and replaced it. But I still get the payload bin error =(
 
Last edited by Directtor,
  • Sad
Reactions: Blythe93
I got a 2002-3539 and black screen issue. This is after updating my ofw firmware to 19 and atmosphere to 18.

I am able to go into EMUMMC and play games etc.
On Stock SYSNAND I get a black screen after the Nintendo logo.
I get the 2002-3539 error when I want to go into CFW Sysnand.
I've spent two days trying to fix this issue. Im losing my mind. I dont want to do a system wipe.
Do you have a modchip installed? If so, check this thread for more info. People that run into that error had a problem with the Dat0 connector.
 
For the past year I've been playing games on a stock OLED running 15.0.1 and I'd like to move the saved game data over from that to my V1 running CFW 17.0.1. Is the only way to get save data off the OLED to use the 'Transfer your save data' feature and then reboot my V1 into OFW to 'Receive Save Data'? If that is the only way, is it as easy as that or are there things I should know about this process in general?

On my V1 I booted into OFW (17.0.1) and somehow a system update is ready to be installed even though the auto update option is turned off in System Settings. I have NOT applied the update and will not until AMS is updated. But now that I am back in CFW, how can I remove that queued update so I don't accidentally install it?

Earlier this year on my V1, I purchased & downloaded a bunch of games from the eShop. One digital game requires updated FW so I can't play it until AMS is updated for 19.x. However, the rest of the games I can play fine in OFW, but I cannot play them in CFW. When I try to launch them in CFW it wants me to turn off Airplane Mode and after doing that when I launch it says "Checking if software can be played" then fails with 2155-8007 which I assume is because of all the blocks in place to prevent connecting to Nintendo servers. (Note: While in CFW, DNS Blocks are in place, I never play online in CFW, airplane mode is almost always enabled, and since I can play in OFW the console isn't banned.) Is the reason the digital games are not working in CFW because this Switch is not the primary Switch on my account?
 
Is the only way to get save data off the OLED to use the 'Transfer your save data' feature and then reboot my V1 into OFW to 'Receive Save Data'?
Not sure if it's necessary to reboot into OFW for that, but you could try whether it works on CFW first. Of course, with DNS MITM in place on the hacked Switch.
The only time I've transferred a save file from a stock to a modded Switch was when I transferred my ACNH save via Island transfer tool from my Lite to my modded v1 Switch and it worked without any issue. Lite works perfectly fine to this day, no issue whatsoever.

On my V1 I booted into OFW (17.0.1) and somehow a system update is ready to be installed even though the auto update option is turned off in System Settings. I have NOT applied the update and will not until AMS is updated. But now that I am back in CFW, how can I remove that queued update so I don't accidentally install it?
Turning off auto updates doesn't mean that it won't download the update the first time it gets connected to the Nintendo servers. If you aren't playing online games or using NSO on your OFW, you can block the updates by setting up 90DNS.

On CFW side, I believe that DBI can remove the pending update for you. If not, you can do it the old-fashioned way by going into a maintenance mode on stock (turn off the Switch, boot into OFW while holding both + and - buttons until the maintenance menu shows up and just exit afterwards).

Is the reason the digital games are not working in CFW because this Switch is not the primary Switch on my account?
Do you have sys-patch or sigpatches installed on your Switch?
 
I have a question, but I'm reading some conflicting information regarding the Switch (Erista) maximum chip clock.

Technically we aren't overclocking the Tegra X1 because the maximum clock rates are 1785MHz and 921MHz for the CPU and GPU, plus 1600MHz for RAM. As long we don't exceed those values we are within spec.

But, even if not overclocking, I heard some people saying that using both the CPU at max speed and the GPU at max speed with RAM it's dangerous... why is that?
The Foxconn leak from years ago before launch had Switch units running at full speed stressed with heavy tests for several days and no problems arised.
My own unit is performing perfectly fine after years of using it at full speed... It would make sense if perhaps we use the CPU at 2GHz and the GPU at 1GHz, since we are actually overclocking there, but I don't understand why some people say that 1785MHz and 921MHz at the same time is dangerous.
 
I have firmware 18.1.0 installed and I installed an update to a game that requires firmware 19.0.0 and master key 18.0 according to the nfo-file and NX fileviewer. The update seems to work fine although I am not on firmware 19. Is it possible that I could experience crashes later in the game or is it always ok if the game starts?
 
I have firmware 18.1.0 installed and I installed an update to a game that requires firmware 19.0.0 and master key 18.0 according to the nfo-file and NX fileviewer. The update seems to work fine although I am not on firmware 19. Is it possible that I could experience crashes later in the game or is it always ok if the game starts?
You'll be just fine. The general rule of saving your game regularly still applies if you hate wasting your time.
 
  • Like
Reactions: Blythe93
I have firmware 18.1.0 installed and I installed an update to a game that requires firmware 19.0.0 and master key 18.0 according to the nfo-file and NX fileviewer. The update seems to work fine although I am not on firmware 19. Is it possible that I could experience crashes later in the game or is it always ok if the game starts?
no you will not
 
  • Like
Reactions: Blythe93
If the is installed correctly on my switch, how long will its life span be ?
Modchip itself , i mean
 

Site & Scene News

Popular threads in this forum