So, there are some games that on its base version can record videos, but after updating, that ability is lost. Latest examples are World War Z and Dying Light Platinum. I happily played on version 0 almost to the end and took some great videos, but now it is impossible. Is there any homebrew, setting or something that can be tweaked so that video capturing ability goes live again?
The fact that on the Version 0 they could do it, means that the devs changed something on purpose. I hope somebody helps with this, please and thank you.
The fact that on the Version 0 they could do it, means that the devs changed something on purpose. I hope somebody helps with this, please and thank you.
I''m using another jig now, and I guess this works. The screen is staying black now.
After connecting with an usb, I start TegraRcmGUI on the pc.
The APX driver is not showing, so in TegraRcmGUI I go to settings and 'install driver'.
At that moment my pc asks me for a password, because it's the pc from work, so I'm not able to continue
We have a computer at home, but that's a macbook. So I guess this works not the same way as for a Windows pc, correct?
can't you push the payload from your phoneI''m using another jig now, and I guess this works. The screen is staying black now.
After connecting with an usb, I start TegraRcmGUI on the pc.
The APX driver is not showing, so in TegraRcmGUI I go to settings and 'install driver'.
At that moment my pc asks me for a password, because it's the pc from work, so I'm not able to continue
We have a computer at home, but that's a macbook. So I guess this works not the same way as for a Windows pc, correct?
Can anyone tell me how to install the on-cart dlc for SMT V? I made a reddit thread about it and someone replied saying 'if you've already hacked your switch just install it, bro'. Like wow, thanks. Could you actually teach me the steps in order to do it please? Like actually explain this to me like I'm a 5-year-old.
I think you just need to dump it, then install it with TinWoo. Or, if you can't use TinWoo, an inferior installer like Awoo or DBI, or an even worse one like Tinfoil, if you really enjoy pain.
Yeah I tried installing tinfoil and it showed up as a blank tile on my home menu lol. I'll try those other apps you mentioned. But what exactly is TinWoo? Like a combination of Tinfoil and Awoo?
I'm sorry, I'm not that familiar with dumping updates then installing them. However I can help you acquire patches that can install the update. Download them from this thread.
CFW and stock firmware are just modes like booting a safe or recovery mode on your computer so fundamentally, that is impossible.
Yes, it removes the anti-SX OS DRM from Awoo Installer and implements HDD support for a lightweight but effective title installer.
Thank you for your answer, what if the user was the same one? I checked and the friend code is the same one on sysnand and emunand.
Hi, I'm new to switch modding but not to console modding, the switch is an entirely different beast altogether. Still, I'm making headway. Now, onto my questions:
I recently bought an old, unpatched switch under 5.x FW. I followed the guide found here and successfully booted from emuNAND into the most recent version of atmosphere and 5.x firmware. I have never taken my switch online since buying it and want to update my switches firmware to 13.2.0 then create a new emuNAND altogether.. I've already wiped my SD card and repartitioned it,I just need to create the new emuNAND. I am confused though, what is the e-fuse risk? Is it from taking my CFW switch online then updating in the system? I know that I need to use daybreak to update CFW but want to know what the process is that pops the fuse so I don't make that mistake. I just want to get my stock switch up to 13.2 and create my emuNAND.
Lastly, in my mind the process to do what I'm trying to achieve is:
•boot stock switch without my SD card inserted and take it online to allow it to update OFW/sysNAND
•after update is complete, system restore then power down
•go through the process of creating emuNAND as well as using lockpick to get prod.keys(I've already done this but is it different after a system restore)
•boot into cfw
•check settings to see that I've actually successfully updated to 13.2 with the most recent version of atmosphere
Am I wrong or missing anything? Is the system restore step just unnecessary steps?
Will my SD card still work with my switch's CFW since factory resetting it makes them not work together?
Why do you think the original owner remained on such a low firmware? I know things are patched out but those are reimplemented with CFW. What other benefits do I have being on such a low FW though?
Can I run 13.2 fw on emuNAND(by creating at.x emuNAND then updating emuNAND with daybreak) but remain on 5.x on sysNAND?
Sorry for so many questions, I just can't seem to find a straight answer to my questions.
I recently bought an old, unpatched switch under 5.x FW. I followed the guide found here and successfully booted from emuNAND into the most recent version of atmosphere and 5.x firmware. I have never taken my switch online since buying it and want to update my switches firmware to 13.2.0 then create a new emuNAND altogether.. I've already wiped my SD card and repartitioned it,I just need to create the new emuNAND. I am confused though, what is the e-fuse risk? Is it from taking my CFW switch online then updating in the system? I know that I need to use daybreak to update CFW but want to know what the process is that pops the fuse so I don't make that mistake. I just want to get my stock switch up to 13.2 and create my emuNAND.
Lastly, in my mind the process to do what I'm trying to achieve is:
•boot stock switch without my SD card inserted and take it online to allow it to update OFW/sysNAND
•after update is complete, system restore then power down
•go through the process of creating emuNAND as well as using lockpick to get prod.keys(I've already done this but is it different after a system restore)
•boot into cfw
•check settings to see that I've actually successfully updated to 13.2 with the most recent version of atmosphere
Am I wrong or missing anything? Is the system restore step just unnecessary steps?
Will my SD card still work with my switch's CFW since factory resetting it makes them not work together?
Why do you think the original owner remained on such a low firmware? I know things are patched out but those are reimplemented with CFW. What other benefits do I have being on such a low FW though?
Can I run 13.2 fw on emuNAND(by creating at.x emuNAND then updating emuNAND with daybreak) but remain on 5.x on sysNAND?
Sorry for so many questions, I just can't seem to find a straight answer to my questions.
Last edited by LegzRwheelz,
yes, create a emunand, then both will have completely separate settings.
fuses only matter to downgrade fw which isnt needed anymore. just boot stock, update to 13.2. turn off, then rcm mode > hekate > make emunand ect. system restore is totally unnecessary and theres 0 benefit to stay on a lower firmware than whats current.
Last edited by Chaosta,
The newest sig patch release (ITotalJustice/patches/releases/tag/13.2.0-1.2.5) says "Starting in 2022 hekate.zip will no longer be included, don't use insanely old guides.". Is Hekate really not recommended anymore?
To each they own, I love and will always use Hekate, esp the toolbox,, but yes it is not needed now as you can push Fusee.primary w Atmos now as the payload.
Well, could any of you give any light on the matter of the videos and updates I posted up there somewhere? It would be awesome if somebody could at least give an explanation, is something that is not quite explained yet, because on V0 some games can record video, then update them and it is gone. What changes? Can it be reverted?
Thank you so very much for such a concise and non-flamatory answer that's so easy to understand...
I tried asking it with as much concision as possible but feel like my head is spinning when I'm typing it out and leaves me feeling like I'm asking the same thing over and over in different ways while missing important parts of my question which ultimately leads to multiple edits and re-edits.
Lastly, I understand sigpatches but am wondering what I need to run to update my sigpatches. I found something called Mariko but don't quite grasp what to do with it. How do I check my current sigpatches to know if they need updating? Oh and if I ever factory reset(I know it's unnecessary), do my prod.keys need redumping (like how the SD card no longer works with the system after a factory reset)?
Oh yeah and the final "lastly" question, lulz... I am a bit confused with the cart slot versioning(switch cartridges). How does someone update their firmware but not the cart slot? Why would they keep the cart slot as a lower version?
Ok ok, one final final "lastly" question. So I know to never ever take the emuNAND Switch online without 90dns (is there still a risk of a ban) and that running emuNAND is essentially like dual-booting the Switch. What I'm wanting to know is if Nintendo would know that my switch has run CFW? Would they know if my switch ran CFW from sysNAND before creating an emuNAND? Would I safely be able to take stock sysNAND Switch online for games like Fortnite and Smash? Should I keep 2 different SD cards so Nintendo doesn't go sniffing around? Thanks again and I'm sorry for so many questions, I hope these questions help others that are confused on the matters like I am.
- No one is chatting at the moment.
-
-
-
@ HiradeGirl:
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
