Homebrew Question HBG shop new update and no full ram access

[aarti]

I just updated my HBG and realized this problem as well. I however figured out a fix, I founded a modded tinfoil which can use hbg / tinfoil without any anti atmosphere DRM.

Simply follow these steps:

1) Drag and drop HBG onto the root of your sd card.

2) Drag and drop the mod found here onto your sd card.

3) Drag and drop the latest version of atmosphere or kosmos onto the root of your sd card.

4) Boot into hbg / tinfoil and copy down the device id it gives you.

5) Put your sd card in your computer and go to switch / tinfoil / mod_config.ini and open it.

6) Delete "enter your tag" and replace it with the device id you copied down.

7) Save the file and put your sd card back into your switch.

8) Boot into HBG / Tinfoil and enjoy!

I take no credit for this app or this mod neither were made by me.

Still can't use tinfoil without mercury

 

[Broduskii]

I am using tinfoil version 4.0 and am not having any issues. I do not have mercury installed, so i have to launch it via the hbmenu.
I agree that forcing users to have mercury is stupid.

 

[Deleted-452294]

Is there a GitHub or a source for the mod you have graciously provided? I'm also wondering how someone releases a modified version of a closed-source application. Or is the ini file where all the magic lies?

https://github.com/coniventia/tinfoilmod-releases/releases

 

[Lacius]

Bad analogy, a better on would be: what if my software removed goldleaf, then installed a slightly modified fork, then refused to run if it wasnt present. I would not have a problem with this, as its still my software, and no rebranding was done.

If the software makes button mapping changes against my will and removes functionality, it's malware.

 

[aarti]

https://github.com/coniventia/tinfoilmod-releases/releases

this one works, thanks

 

[Dave_Chad]

I still don't understand what exactly the Atmosphere bundled with HBG "fixes". I've been using vanilla Atmosphere with no issues.

I wish HBG was just an app and not something that hijacks your CFW install. The app is an amazing thing and I want to keep using it but it seems to be getting more difficult [emoji853]

Sent from my VOG-L09/Huawei P30 Pro

 

[Lacius]

I still don't understand what exactly the Atmosphere bundled with HBG "fixes". I've been using vanilla Atmosphere with no issues.

I wish HBG was just an app and not something that hijacks your CFW install. The app is an amazing thing and I want to keep using it but it seems to be getting more difficult [emoji853]

Sent from my VOG-L09/Huawei P30 Pro

It doesn't "fix" anything. It breaks it.

 

[blawar]

I still don't understand what exactly the Atmosphere bundled with HBG "fixes". I've been using vanilla Atmosphere with no issues.

I wish HBG was just an app and not something that hijacks your CFW install. The app is an amazing thing and I want to keep using it but it seems to be getting more difficult [emoji853]

Sent from my VOG-L09/Huawei P30 Pro

because atmosphere broke memory in applets and blocks bis writes for no reason.

 

[ErnieBall]

because atmosphere broke memory in applets and blocks bis writes for no reason.

Both of these issues are easily fixed. Noone should use applet mode in atmosphere, unless they have to (injecting cheats while a game is running).
Incognito can be installed using a sysmodule.

 

[blawar]

Both of these issues are easily fixed. Noone should use applet mode in atmosphere, unless they have to (injecting cheats while a game is running).
Incognito can be installed using a sysmodule.

Running Tinfoil in title mode is unsupported, running small homebrew apps in title mode is dumb and increases SD corruption. The sys module is cancer, bad UX.

 

[Mopquill]

because atmosphere broke memory in applets and blocks bis writes for no reason.

See:

Both of these issues are easily fixed. Noone should use applet mode in atmosphere, unless they have to (injecting cheats while a game is running).
Incognito can be installed using a sysmodule.

@blawar No one is on your side here dude, you're breaking people's CFW in a way that suits you and you alone, for a use people are not even intending to download tinfoil for. And what's baffling is, it takes a lot more work on your part to maintain this! Here are some ideas:

- You could provide this patched atmosphere with incognito only.
- You could provide patches in the folders atmosphere provides for this exact kind of purpose and achieve the same effect, with the ability to remove them after the fact, as a separate bundle for people who want a "one-click" setup.
- You could do the above, but with incognito only.
- You could provide directly-patched atmosphere (for whatever reason why this is better than providing patch files that can be dropped in) as a separate bundle for the same purpose.
- You could write a simple few paragraphs explaining this to end-users, and telling them you don't like supporting Atmosphere, and it may introduce the following issues, and they can get ReiNX if they want.

Incognito, besides it not being unnecessary to bundle it with tinfoil, should only be running once. Why permanently mod the CFW *and bundle those mods* with your software? And then -require- they be used, or refuse to run? That is DRM, and it's modifying people's systems while masquerading as an all-in-one pack. Why not just provide ReiNX with your bundle if you're gonna force people to make CFW changes? Why not control the entire software suite on a user's device? Where is the line here?

It's bad enough your code is closed source, which makes people wonder if there's questionable shit in there, but you're actually making people doubt your motives, and considering which actions you're taking publicly, what the hell other ones are you taking that we don't know about? It's not like this was announced, it was all just silently included in the update, it's totally messed up.

Running Tinfoil in title mode is unsupported, running small homebrew apps in title mode is dumb and increases SD corruption. The sys module is cancer, bad UX.

That is total bullshit, unless you're talking about exFAT, which users should not be formatting their cards in anyhow. The hell do you mean running it in title mode is unsupported? Why!? Even with your patches, downloading in applet mode still causes crashes, because there isn't enough memory. How is the sysmodule bad UX? How the hell is *replacing users files* without their awareness or consent and breaking all title launching because you don't want your app to support it (even if you're gone back on this point) *not* bad UX? Please, enlighten us.

 

[blawar]

See:


@blawar No one is on your side here dude, you're breaking people's CFW in a way that suits you and you alone, for a use people are not even intending to download tinfoil for. And what's baffling is, it takes a lot more work on your part to maintain this! Here are some ideas:

- You could provide this patched atmosphere with incognito only.
- You could provide patches in the folders atmosphere provides for this exact kind of purpose and achieve the same effect, with the ability to remove them after the fact, as a separate bundle for people who want a "one-click" setup.
- You could do the above, but with incognito only.
- You could provide directly-patched atmosphere (for whatever reason why this is better than providing patch files that can be dropped in) as a separate bundle for the same purpose.
- You could write a simple few paragraphs explaining this to end-users, and telling them you don't like supporting Atmosphere, and it may introduce the following issues, and they can get ReiNX if they want.

Incognito, besides it not being unnecessary to bundle it with tinfoil, should only be running once. Why permanently mod the CFW *and bundle those mods* with your software? And then -require- they be used, or refuse to run? That is DRM, and it's modifying people's systems while masquerading as an all-in-one pack. Why not just provide ReiNX with your bundle if you're gonna force people to make CFW changes? Why not control the entire software suite on a user's device? Where is the line here?

It's bad enough your code is closed source, which makes people wonder if there's questionable shit in there, but you're actually making people doubt your motives, and considering which actions you're taking publicly, what the hell other ones are you taking that we don't know about? It's not like this was announced, it was all just silently included in the update, it's totally messed up.


That is total bullshit, unless you're talking about exFAT, which users should not be formatting their cards in anyhow. The hell do you mean running it in title mode is unsupported? Why!? Even with your patches, downloading in applet mode still causes crashes, because there isn't enough memory. How is the sysmodule bad UX? How the hell is *replacing users files* without their awareness or consent and breaking all title launching because you don't want your app to support it (even if you're gone back on this point) *not* bad UX? Please, enlighten us.

Title mode causes corruption because it is impossible to exit an app cleanly, you are basically force killing it every time. Native Nintendo titles do not write to the SD card at all, they only write to save files which are journaled / highly durable, and designed for sudden killing and recovery. You are simply not supposed to access the SD card at all from title mode. There are other inherent problems with running in title mode, that admittedly, I could partially work around but don't because title mode is not supported.

I do not replace anyone's files without consent, it clearly states it includes an atmosphere fork.

 

[Mopquill]

Title mode causes corruption because it is impossible to exit an app cleanly, you are basically force killing it every time. Native Nintendo titles do not write to the SD card at all, they only write to save files which are journaled / highly durable, and designed for sudden killing and recovery. You are simply not supposed to access the SD card at all from title mode. There are other inherent problems with running in title mode, that admittedly, I could partially work around but don't because title mode is not supported.

I do not replace anyone's files without consent, it clearly states it includes an atmosphere fork.

View attachment 179671

That is valid, if true. I don't know enough about how the Switch saves data specifically to validate it, but ext4 is journaled, and FAT isn't, and that generally makes some sense. Look, believe me, I get not wanting to work on something that is specifically more difficult to support, but outright blocking people's ability to use the app anyhow is a rather heavy-handed response to that, don't you think? I have been using Tinfoil via title mode to write all my physical games to a 512GB SD card in FAT32. I'm 200-something GB in, and ran out of games to scan. Everything has been fine, and I just took the time to check, and I have 0 corruption on my card. I'm content with installing updates this way, so having the application disallow it is super frustrating.

That notice was not there when I downloaded (I originally found out about this because title mode launching was not working, and I found this thread), though it's much better that it's there now. I still think utilizing the function of one of the patches folders would be a much better approach.

You said Atmosphere started this. Have you tried filing an issue on the Github or something?

 

[wurstpistole]

Still can't use tinfoil without mercury

Wrong. Follow the steps and it works. DO NOT copy ANYTHING ELSE from HBGshop pack than the switch/tinfoil folder. No HBmenu, no HBL no forwarders nothing. Only the tinfoil folder, and then replace files with mod. Done.

 

[cYcLoNe_AUT]

I really have to say, I´m at a loss here. I tried this steps with hbgshop pack 4.00 and 4.10. I tried it with hpl.nsp 2.1 and 2.2... It always says that the install environment is corrupt. And yes, I only took the files from switch/tinfoil folder in these packs. Could it be, that the mod doesn´t work with cosmos?

 

[blawar]

You said Atmosphere started this. Have you tried filing an issue on the Github or something?

I am banned from creating issues on Atmosphere's github for "being blawar". Even if I was not, Tinfoil is the only app affected by the change that supported applet mode, and they will not entertain any issues about Tinfoil. Atmosphere forced me to either fork or drop Atmosphere support.

--------------------- MERGED ---------------------------

I really have to say, I´m at a loss here. I tried this steps with hbgshop pack 4.00 and 4.10. I tried it with hpl.nsp 2.1 and 2.2... It always says that the install environment is corrupt. And yes, I only took the files from switch/tinfoil folder in these packs. Could it be, that the mod doesn´t work with cosmos?

If you are running Atmosphere, you have to copy all files from the pack to run the custom fork. Vanilla atmosphere is not supported.

 

[wurstpistole]

If you are running Atmosphere, you have to copy all files from the pack to run the custom fork. Vanilla atmosphere is not supported.

... Except if one is using the mod which I have no doubt about that you will go to all possible lengths to block it in the next release

 

[blawar]

... Except if one is using the mod which I have no doubt about that you will go to all possible lengths to block it in the next release

Not a priority, I have bigger issues to fry with libnx / DKP on 9.0.0.

 

[OrGoN3]

The reason this only affects atmosphere, is because atmosphere has been implementing more features that cause problems: the bis write protections, reducing applet memory usage by 30%, and to a lesser extent changing album hotkey behavior with no way to revert back to previous behavior.

You can set the applet memory usage back to normal manually in the config file though.

 

[hippy dave]

While everyone would agree you have big issues, you could probably find better ways to spend your energy.