Hacking SWITCH NOOB PARADISE - Ask questions here

[Psd99]

Great then that should absolutely be the correct path. I'll try it out on my Switch after work.

Not saying your idea is noobish at all. You might be on to something.


Cheats are going to be under /atmosphere/contents/<gameID>/cheats I believe. See if there's anything there for you.

Do u mean like check on the original SD card and copy it over to the new card?

 

[Prior22]

Is the only way to update tinfoil by downloading from their website. Or is it possible to update tinfoil via the app itself? Thanks

 

[binkinator]

Do u mean like check on the original SD card and copy it over to the new card?

correct. each game you have cheats for should have that directory structure. you will need to copy it over if you have something specific.

You can also cheat the cheats and just a tool like Breeze to grab the cheats for your installed games (probably easier/faster.)

https://github.com/tomvita/Breeze-Beta

 

[YuriH]

So I updated my firmware and I don't know what I did to get Atmosphere CFW on it how to remove it?

 

[Draxzelex]

So I updated my firmware and I don't know what I did to get Atmosphere CFW on it how to remove it?

Unless you were using SX OS, you always had Atmosphere and since its the only CFW left, I don't know why you would want to remove it unless you're done with CFW.

 

[binkinator]

Is the only way to update tinfoil by downloading from their website. Or is it possible to update tinfoil via the app itself? Thanks

It will update itself when you start the app as well. Just start Tinfoil and let it go.
(If it doesn’t work, then yeah, you’ll have to download the new tinfoil.nro self installer and install over the top. Great instructions in the Download section of tinfoil.io.)

 

[nickieemp]

Is the only way to update tinfoil by downloading from their website. Or is it possible to update tinfoil via the app itself? Thanks

I just pressed the + sign-> Data management -> delete software, then downloaded and updated the tinfoil self installer in the sd card, opened up Homebrew (click R and then open any game) and then reinstalled

 

[YuriH]

Unless you were using SX OS, you always had Atmosphere and since its the only CFW left, I don't know why you would want to remove it unless you're done with CFW.

I wasn't, just wondering why that showed up there since it never showed up there before well I'll just leave it alone.

 

[Draxzelex]

I wasn't, just wondering why that showed up there since it never showed up there before well I'll just leave it alone.

That depends, how did you update?

 

[YuriH]

That depends, how did you update?

I updated the SysNAND first then dumped it to updated the EmuNAND updated it via Daybreak.

 

[Draxzelex]

I updated the SysNAND first then dumped it to updated the EmuNAND updated it via Daybreak.

You didn't use any external tools to update your CFW?

 

[YuriH]

You didn't use any external tools to update your CFW?

I updated via my PC removing the micro SD card.

 

[Draxzelex]

I updated via my PC removing the micro SD card.

Did you update your hekate_ipl.ini file as well?

 

[YuriH]

Did you update your hekate_ipl.ini file as well?

I did.

 

[Draxzelex]

I did.

How did you update it?

 

[elecu]

Move emummcforce=1 underneath [Atmosphere CFW]

like this:

Post automatically merged: Oct 19, 2022

I’m not 100% sure of the location. It looks correct. I assume the directory tree is there only for games that you‘ve installed and played one time on the new setup? Meaning that games you’ve installed but not played yet don’t have this available yet, correct? Your suggestion about copying the /USER/Saves is a great one…I can’t help But think that if it worked like that, how come veryone isn;t doing it like that? There has to be something that screws up. If you are going to try it, either make a backup or be prepared to make a new Emunand.

Well, I did that, and it didn't work. Black screen after logo again.

So, I created a new emuMMC in the emuMMC Manage menu with the SD Partition, which made a copy of my Sysnand. I reaccessed it under Launch, Atmosphere CFW, and it loaded fine. I could see the E at the end of the version in the System Menu.

So I thought I could restore the backup I had. With my old SD, I created it by going to Tools, Backup eMMC, turning on the SD emuMMC Raw Partition and selecting SD emuMMC BOOT0 & BOOT1 plus SD emuMMC RAW GPP. So that's the backup I have.

Then, after the new emuMMC was working, to recover my last backup where I had these saves. I went to Tools, Restore eMMC, turned on the SD emuMMC Raw Partition, and again SD emuMMC BOOT0 & BOOT1 plus SD emuMMC RAW GPP. Previously I moved from the backup/### files into the backup/###/Restore folder.

Again, I have this black screen when I select Atmosphere CFW after the logo. I think I am doing something wrong, but at least I know a new emuMMC could work. I'd like to recover my saved data from my old SD. Any idea what I'm doing wrong?

 

[binkinator]

Well, I did that, and it didn't work. Black screen after logo again.

So, I created a new emuMMC in the emuMMC Manage menu with the SD Partition, which made a copy of my Sysnand. I reaccessed it under Launch, Atmosphere CFW, and it loaded fine. I could see the E at the end of the version in the System Menu.

awesome. This is exactly what we needed to see. Nice work.

So I thought I could restore the backup I had. With my old SD, I created it by going to Tools, Backup eMMC, turning on the SD emuMMC Raw Partition and selecting SD emuMMC BOOT0 & BOOT1 plus SD emuMMC RAW GPP. So that's the backup I have.

that is the correct way to make a backup.

Then, after the new emuMMC was working, to recover my last backup where I had these saves. I went to Tools, Restore eMMC, turned on the SD emuMMC Raw Partition, and again SD emuMMC BOOT0 & BOOT1 plus SD emuMMC RAW GPP. Previously I moved from the backup/### files into the backup/###/Restore folder.

this is the correct way to move your backup to the restore folder

Again, I have this black screen when I select Atmosphere CFW after the logo. I think I am doing something wrong, but at least I know a new emuMMC could work. I'd like to recover my saved data from my old SD. Any idea what I'm doing wrong?

This should have worked. It seems your backup might not be good.

One thing we can try is to use EmuTool on your PC to copy your partition based emunand to a files based Emunand so you can copy it off your old SDcard to your new SDCard as regular files and then use Hekate to switch over to a files based emunand to see if we can get it to work. You will be able to swap back to partition based emunand by just reversing the steps in Hekate. It’s a long shot but we might get lucky. If it works we can use JKSV to dump your saves, switch back to partition based emunand then use JKSV to import your saves back to the fresh emunand partition you just made. A bit of work for sure. You will still have to reinstall your games again but at least you would have your saves.

Another way would be to simply use NXNandManager on your PC to dump the game saves from the USER/saves partition. You will need to dump your prod.keys using Lockpick_RCM to enable the yellow explorer folder so you can browse the mounted USER partition. You would reinstall your games and import them with JKSV just the same but with fewer steps.

 

[YuriH]

How did you update it?

Well I just went back and changed it to the one from here https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/ and now it's gone and it now looks like this.

 

[nachopitt]

Hello.

Do you know if the files generated by the grit tool (binary for bin2s and C source and header file) are compatible with Nintendo Switch Homebrew development (devkitpro and libnx) ? I've been trying to display some BMPs and PNGs on the NS Framebuffer (PIXEL_FORMAT_RGBA_8888) which, correct me if I'm wrong, the grit tool is able to covert them to 16 bits at most (RGB565). Due to this setup (RGB565 -> RGB8888) I know some conversion has to be made to keep things in sync. However, no matter how I configure the BIN RGB images using grit, the result is not the one I want. Probably I'm not passing the correct parameters to the grit tool when generating the assets. So if you have any idea what could be wrong in my side that could be great. Maybe grit is not the right tool to be used in Switch homebrew development.

So far this is the grit command line I'm using right now:
grit assets/${file}.png -g -gb -gB16 -gT! -ftb -fh!

But I've tried also with BMP files in mind by just changing extension

I've also used the BIN files generation instead of C Source and Header files generation but that leads to the same problem:
grit assets/${file}.png -g -gb -gB16 -gT! -ftc
In the attachments you will find how it looks right now and how it should look like (probably with a little bit less quality)

If I'm using the wrong tool for the job, would you mind pointing me with the right tool?

Thanks a lot for your time and your help.

 

[cob764]

that file was ldn (lan play)

Post automatically merged: Oct 20, 2022

it was ldn lan play