Ok, so I figured it out. Holding power seemed to just flash the atmosphere logo. I removed the sd card, put the updated files on it, and put it back in. At first it seemed to not do anything, but holding power eventually did allow me to power off and boot into ofw, so I just restarted the process. Thank you all anyways!
that’s good, and bad. Good in that it’s not something inherent to Tinfoil, but bad that it doesn’t solve the issue.
We can wait a bit and see if anyone else has seen this issue, but yeah…if you want to update in the meantime, you’ll probably have to grab the base again.
Hi All,
Any help appreciated, accidentally updated after installing hekate and atmos.
Everything was working fine until I updated.
I can still inject, but when I load cfw, I get a black screen.
Thank You.
Wayne
Any help appreciated, accidentally updated after installing hekate and atmos.
Everything was working fine until I updated.
I can still inject, but when I load cfw, I get a black screen.
Thank You.
Wayne
likely suspects will be
1) fusee.bin not updated and placed in /bootloader/payloads
https://rentry.org/SwitchHackingIsEasy
2) upgraded from old version of atmosphere and didn’t clean up directories and fix /bootloader/hekate_ipl.ini
https://rentry.org/MigrateToAtmosphere1_0_0
3) didn’t update Sigpatches
- Sigpatches (GBATemp) — alternative Sigpatches for when others don’t seem to work.
- Sigpatches — get your iTotalJustice Sigpatches here (with free instructions!)
e: might want to update your injector payload while you’re at it.
Hope someone can help me with this.
At the moment, I am not sure which version I'm using.
The one that is currently installed in my switch requires me to run a program called 'TegraRcmGUI.exe'
every time my switch ran out of battery (from 0%) and inject the payload before it turns itself on.
My question is - I wish to update my CFW to the version where I don't have to inject payload every time
the switch ran out of battery. Is it even possible?
Also - I am looking to play some PSP games in the switch if someone can direct me to the right page?
At the moment, I am not sure which version I'm using.
The one that is currently installed in my switch requires me to run a program called 'TegraRcmGUI.exe'
every time my switch ran out of battery (from 0%) and inject the payload before it turns itself on.
My question is - I wish to update my CFW to the version where I don't have to inject payload every time
the switch ran out of battery. Is it even possible?
Also - I am looking to play some PSP games in the switch if someone can direct me to the right page?
If you are using the RCM exploit, then if your battery dies, you have to resend the payload. The easy solution to this is to not let your system die. There are hardware modifications that you can install to get around this.
It is in FAT32 and there wasn't any issue with it when I connected it to try to update Hekate, Fusee, and Atmosphere.
[config]
autoboot=0
autoboot_list=0
bootwait=3
autohosoff=0
autonogc=1
updater2p=0
backlight=100
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp
Thanks for the help.
Nothing untoward in your .ini file. You don’t have an autoboot set, yet you’re not even seeing hekate…it‘s got to be before that.
How do you have you SX dongle set up to boot hekate?
- Did you build hekate.x.x.x.bin into a boot.dat file?
- Did you download SX_Gear_v1.1.zip and move hekate.x.x.x.bin to payload.bin?
Last edited by binkinator,
I'm going to be honest with you, I'm not entirely certain which way I'm doing it. I'm going to assume it is which ever method was easiest to change to from SXOS. I'm using the SXOS pro dongle, I don't know if that clears things up at all.
Is there a way that I can definitively figure this out?
yo sorry for being all over the place first of all LOL, but quick question.
well not sure if i should ask here or in the switch bans thread, but connecting to the internet with a cfw switch is safe right? just as long as i dont go online with a nonlegit nsp? thats my understanding of switch bans at least..
No worries. If your Emunand is a copy of a clean Sysnand and all you’re doing is CFW, that’s what Atmosphere is for. The issue is that people forget what they’ve done so as a general rule we tell people that clean Sysnand is for Online and dirty Emunand is for offline. There are other things such as changing your Profile Avatar or using Cheats in Online games that you can read about in the Switch Ban Hub thread.
Probably easier to just walk through this guide and it will get you to a known state (rather than reverse engineering what you have right now): https://rentry.org/mys8q
The password is: Trinket M0
will save you a Google:
Trinket M0 Hardware — The @mattytrog Bible for installing the Trinket M0
Trinket M0 Software — The @mattytrog encyclopedia of Trinket M0 software (source here https://github.com/mattytrog/FUSEE_SUITE)
ohh ok perfect yea explains why my first hacked switch got banned.
my goal is to play with some infinite health codes for metroid for some routing tests, but with my specific save file. would I just download the save file on the sysnand then use the codes on my emunand then? would that work or will the save file not be on the emunand?
You really should do that on Emunand with exosphere and dns:mitm installed so you can be connected to the Internet (but in no way connected to Ninty.)
https://rentry.org/ExosphereDNSMITM
Once this is set up it will allow you to safely download the save file to your Emunand.
Emunand is a point in time copy of your Sysnand. Once the copy is made they are for all intents and purposes two completely separate “machines” (that just happen to use the same underlying hardware to run one at a time.)
Last edited by binkinator,
you were responding to a two year old thread. You’re more likely to get help here.
Did you recently upgrade your Firmware or Atmosphere and now you’re getting a black screen? Please give as much detail as possible About your issue.
hey so im trying to connect to the save data cloud to downland the save, but i get error code 2155 8007. btw i set up exoshphere and dns:mitm exactly how you said.
